db-derby-user mailing list archives

> I suspect that the database cache is returning this old information.

Perhaps the transaction which is updating the information has not
yet committed, and the transaction which is trying to fetch the
information is running at READ COMMITTED isolation level. In that
case, the database will happily return the old information. See:
http://db.apache.org/derby/docs/10.3/devguide/cdevconcepts15366.html

thanks,

bryan