This Bored
#11
(07-19-2020, 08:47 AM)MassDebater Wrote:
(07-19-2020, 06:58 AM)Midget In A Pinstripe Suit Wrote: I’m no expert but I think it’s to do with the database freaking out when it reaches a certain capacity. I’m sure Birdy is well aware.

Sounds like Foreign and Primary key values are getting mixed up. It's an odd one and my money would be there being a problem with the front end code, somehow it mixes up the ID of the post when creating the reply. The going to the last page one is well odd, would suggest that the post creation code is pulling a default date (which is ancient) and using that (although that default could be set in the database table and is being used because the front end has lost the information at some point). Databases tend to behave consistently, front ends can be flaky and send incorrect information to them a lot...bloody coders are lazy sods, I know because I am!

Whatever it is, it sounds bloody painful and time consuming to fix (heck even finding out which bit is cocking up will be a pain and half)
That's exactly what I thought, it's fooked. Wink
Reply
#12
(07-19-2020, 09:29 AM)Tom Joad Wrote:
(07-19-2020, 08:47 AM)MassDebater Wrote:
(07-19-2020, 06:58 AM)Midget In A Pinstripe Suit Wrote: I’m no expert but I think it’s to do with the database freaking out when it reaches a certain capacity. I’m sure Birdy is well aware.

Sounds like Foreign and Primary key values are getting mixed up. It's an odd one and my money would be there being a problem with the front end code, somehow it mixes up the ID of the post when creating the reply. The going to the last page one is well odd, would suggest that the post creation code is pulling a default date (which is ancient) and using that (although that default could be set in the database table and is being used because the front end has lost the information at some point). Databases tend to behave consistently, front ends can be flaky and send incorrect information to them a lot...bloody coders are lazy sods, I know because I am!

Whatever it is, it sounds bloody painful and time consuming to fix (heck even finding out which bit is cocking up will be a pain and half)
That's exactly what I thought, it's fooked. Wink

It's your bloody untested top wot did it!
Reply
#13
(07-19-2020, 09:24 AM)MassDebater Wrote:
(07-19-2020, 09:23 AM)Pickle Rick Wrote:
(07-19-2020, 08:47 AM)MassDebater Wrote:
(07-19-2020, 06:58 AM)Midget In A Pinstripe Suit Wrote: I’m no expert but I think it’s to do with the database freaking out when it reaches a certain capacity. I’m sure Birdy is well aware.

Sounds like Foreign and Primary key values are getting mixed up. It's an odd one and my money would be there being a problem with the front end code, somehow it mixes up the ID of the post when creating the reply. The going to the last page one is well odd, would suggest that the post creation code is pulling a default date (which is ancient) and using that (although that default could be set in the database table and is being used because the front end has lost the information at some point). Databases tend to behave consistently, front ends can be flaky and send incorrect information to them a lot...bloody coders are lazy sods, I know because I am!

Whatever it is, it sounds bloody painful and time consuming to fix (heck even finding out which bit is cocking up will be a pain and half)

Or storage areas over writing other ones.... anyhow, it all adds to the excitement - you could end up posting as Baggy Mad

Could be worse, I could end posting as Baggii and having to contact my employer to sack me for being on here!

Does he post on here? I was a massive fan of his.... that’s sarcasm btw Wink
Reply
#14
(07-19-2020, 09:23 AM)Pickle Rick Wrote:
(07-19-2020, 08:47 AM)MassDebater Wrote:
(07-19-2020, 06:58 AM)Midget In A Pinstripe Suit Wrote: I’m no expert but I think it’s to do with the database freaking out when it reaches a certain capacity. I’m sure Birdy is well aware.

Sounds like Foreign and Primary key values are getting mixed up. It's an odd one and my money would be there being a problem with the front end code, somehow it mixes up the ID of the post when creating the reply. The going to the last page one is well odd, would suggest that the post creation code is pulling a default date (which is ancient) and using that (although that default could be set in the database table and is being used because the front end has lost the information at some point). Databases tend to behave consistently, front ends can be flaky and send incorrect information to them a lot...bloody coders are lazy sods, I know because I am!

Whatever it is, it sounds bloody painful and time consuming to fix (heck even finding out which bit is cocking up will be a pain and half)

Or storage areas over writing other ones.... anyhow, it all adds to the excitement - you could end up posting as Baggy Mad

Arf!

I’ve seen our servers behave weirdly when BST time kicks in, can NTT play a part as well?
In the form of his life.
Reply
#15
(07-19-2020, 10:33 AM)Midget In A Pinstripe Suit Wrote:
(07-19-2020, 09:23 AM)Pickle Rick Wrote:
(07-19-2020, 08:47 AM)MassDebater Wrote:
(07-19-2020, 06:58 AM)Midget In A Pinstripe Suit Wrote: I’m no expert but I think it’s to do with the database freaking out when it reaches a certain capacity. I’m sure Birdy is well aware.

Sounds like Foreign and Primary key values are getting mixed up. It's an odd one and my money would be there being a problem with the front end code, somehow it mixes up the ID of the post when creating the reply. The going to the last page one is well odd, would suggest that the post creation code is pulling a default date (which is ancient) and using that (although that default could be set in the database table and is being used because the front end has lost the information at some point). Databases tend to behave consistently, front ends can be flaky and send incorrect information to them a lot...bloody coders are lazy sods, I know because I am!

Whatever it is, it sounds bloody painful and time consuming to fix (heck even finding out which bit is cocking up will be a pain and half)

Or storage areas over writing other ones.... anyhow, it all adds to the excitement - you could end up posting as Baggy Mad

Arf!

I’ve seen our servers behave weirdly when BST time kicks in, can NTT play a part as well?

Are they running ZX Spectrums in Raid 5 down on your server farm or something?!?! Wink
Reply
#16
(07-19-2020, 09:41 AM)MassDebater Wrote:
(07-19-2020, 09:29 AM)Tom Joad Wrote:
(07-19-2020, 08:47 AM)MassDebater Wrote:
(07-19-2020, 06:58 AM)Midget In A Pinstripe Suit Wrote: I’m no expert but I think it’s to do with the database freaking out when it reaches a certain capacity. I’m sure Birdy is well aware.

Sounds like Foreign and Primary key values are getting mixed up. It's an odd one and my money would be there being a problem with the front end code, somehow it mixes up the ID of the post when creating the reply. The going to the last page one is well odd, would suggest that the post creation code is pulling a default date (which is ancient) and using that (although that default could be set in the database table and is being used because the front end has lost the information at some point). Databases tend to behave consistently, front ends can be flaky and send incorrect information to them a lot...bloody coders are lazy sods, I know because I am!

Whatever it is, it sounds bloody painful and time consuming to fix (heck even finding out which bit is cocking up will be a pain and half)
That's exactly what I thought, it's fooked. Wink

It's your bloody untested top wot did it!

AAaagh. Thought I'd got away with that. It's consigned to the wash basket and will never view another game.
Reply
#17
(07-19-2020, 10:35 AM)MassDebater Wrote:
(07-19-2020, 10:33 AM)Midget In A Pinstripe Suit Wrote:
(07-19-2020, 09:23 AM)Pickle Rick Wrote:
(07-19-2020, 08:47 AM)MassDebater Wrote:
(07-19-2020, 06:58 AM)Midget In A Pinstripe Suit Wrote: I’m no expert but I think it’s to do with the database freaking out when it reaches a certain capacity. I’m sure Birdy is well aware.

Sounds like Foreign and Primary key values are getting mixed up. It's an odd one and my money would be there being a problem with the front end code, somehow it mixes up the ID of the post when creating the reply. The going to the last page one is well odd, would suggest that the post creation code is pulling a default date (which is ancient) and using that (although that default could be set in the database table and is being used because the front end has lost the information at some point). Databases tend to behave consistently, front ends can be flaky and send incorrect information to them a lot...bloody coders are lazy sods, I know because I am!

Whatever it is, it sounds bloody painful and time consuming to fix (heck even finding out which bit is cocking up will be a pain and half)

Or storage areas over writing other ones.... anyhow, it all adds to the excitement - you could end up posting as Baggy Mad

Arf!

I’ve seen our servers behave weirdly when BST time kicks in, can NTT play a part as well?

Are they running ZX Spectrums in Raid 5 down on your server farm or something?!?! Wink

Arf! No, but as a lot of it is video/time based stuff any discrepancies have severe issues down the line.
In the form of his life.
Reply


Forum Jump:


Users browsing this thread: