[msql-list] Query about a possible Select bug (bad pun intended)
Paul McGougan
We have an very old installation of MSQL (version 2.0.9) that recently
exhibited an odd thing.
Wait! I know you all want to just start replying straight away with the
standard "That's an old version. You should upgrade." response, but please
don't. Due to policy that will be extremely hard to do and it won't answer
my question.
The problem:
An automated process performed a select query on our database but appeared
to miss a row (i.e. it did not return it in the result) that we knew to be
in the table.
The same process when running again the next day then returned a result that
correctly included the row that was seemingly missing in the previous run.
So my actual question is, is this sort of a bug a known issue for 2.0.9? If
so, is there a known work-around.
Thanks for your time.
Regards,
Paul McGougan
Braintree Communications Pty Ltd
--
This information together with any attachments is for the use of the
intended recipient(s) only and may contain confidential and/or privileged
information and is subject to copyright. If you have received this email in
error please inform the sender as quickly as possible and delete this email
and any copies of this information from your computer system network. If you
are not the intended recipient of this email, you must not copy, distribute
or take any action(s) that relies on this information. Any form of
disclosure, modification, distribution and/or publication of this email is
strictly prohibited.
-----------------------------------------------------------------
This is the Mini SQL Mailing List operated by Hughes Technologies
To unsubscribe, go to http://www.Hughes.com.au/extras/email/
David J. Hughes
OK, firstly, you are correct. That's a very old version and many, many
issues have been addressed since then. If you must stay with 2.x then
you should at least be running 2.0.12. That's much newer - it's was
only released in Sep 2001 !!
As for the problem you outline, no, it's not a known issue. The only
thing I can think of is that perhaps an index has been corrupted on
that table. If there are indices on that table then it would be a good
idea to drop and re-create them just in case.
Bambi
..