Dork wrote:stargeezer wrote:As long as it is not used beer, can I have another.
So as far as the bug goes, am I correct in assuming that all of the necessary data is available, but there is no time or interest to fix it. Times sure change. When I was programming, if there was a problem in my code, I did not sleep until I got it fixed. This must be code of someone that is no longer available for whatever reason and the support staff just does not want to dig.
Support staff? BAHAHAHAAA!!! There ain't nobody driving this bus. We're just lucky to be on a relatively straight road. Hopefully it will last long enough for me or someone else to get to the front and figure out how to work the controls.
I've been using this board for years and have never heard of this bug. Then again, I pretty much never visit these huge threads. I went through 6 pages and still don't quite understand what you guys are saying.
If someone could explain what's going on in this bug reports thread (or a new thread if you'd like) I'd appreciate it:
Dork wrote:When a message is posted, records are inserted into several different tables, two of them being POSTS and POSTS_TEXT. What appears to be happening here is that occasionally, there is no record in POSTS_TEXT. Some queries join to this table, some don't so they get different numbers of posts.
hmm... i still dont know what the resync thing was in the first place, but i wonder if part of it did referential checks and corrected mis-matches?
Dork wrote:Ok, I looked again with a clear head and there were 73 bad posts. 4 were from long ago, the rest were all from August 18th so I don't think it's a recurring problem requiring some big coding project. I removed the posts and did a resync which I *think* have fixed it.
Please start posting in the bar again and let me know how it goes
Users browsing this forum: No registered users and 1 guest