Hi,

I ran into a strange problem yesterday concerning query results. I found
that if I ran the same query twice in a row, each in it's own transaction, I
got a different number of results. The first time, I got the correct number
of results, but the second time, I only got the first result... the rest
were missing.

The same thing happened when I ran one query and then another that should
have yielded a sub-set of the first.

I had had my cache type set to none. When I set it back to the default, the
problem went away.

I haven't explored my test cases far enough to narrow in on the problem... I
don't think it's as broad as: running the same query twice yields different
results when caching is set to none.

I'll come up with some code to demonstrate it and post it on the list later
today... I just wanted to throw it out there first and see if anyone had any
quick answers.

Thanks!

-Will Conant

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
        unsubscribe castor-dev

Reply via email to