Alexei Novakov wrote:
> --- Jey Razack <[EMAIL PROTECTED]> wrote:
>> DB Version : 7.5.00.24
>> OS Redhat 2.4.22-1.2199 i686 athlon i386 GNU/Linux
>>
>> Immediately after data insert (COMMIT after each
>> insert), the 'COUNT' function on a table (2.3
>> million records)
>> generates wrong result (higher than the actual).
> I wonder if this might be related to the problem I
> encountered a while ago with MaxDB 7.5.0.18. I was
> properly, but not 100% sure. I was able to get rid of
> the problem after I dropped unique index on this
> table. Hope this helps.
I remember having trouble with COUNT statements producing
effectively random results. One COUNT would return X, the
next (seconds later) would return Y.
That was caused by a damaged index. Dropping and recreating
the index fixed it.
--
Christian Ullrich . "Der Gärtner betrachtet die Rebellen also als
. Unkraut und reinigt seinen Garten von Salat-
Registrierter . verweigerern, indem er Cairol mit seiner Wal-
Linux-User #125183 . ze auf Unkrautjagd schickt." -- Atlan
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
