Hi Enrique,
Enrique Medina wrote:
My question is about executing a direct UPDATE SQL statement and cache management.
I have seen at the FAQs that it is possible to directly execute an SQL statement, through the java.sql.Connection or using a QueryBySQL object.
But what happens with cache in both cases?
The cache will be bypassed in both cases.
a) Directly through the java.sql.Connection --> What happens with cache? Because no OJB API is used, so it would became incosistent.
yes, in this case the user has to take care of cache consistence.
b) Using a QueryBySQL --> Does OJB manage the cache then? How is this done?
AFAIK currently not. We plan to synchronize cache when PB#deleteByQuery was called in 1.1 (by materialize the Identity objects of deleted rows before sql-update call is done and remove objects from cache first)
regards, Armin
Thanks in advance, Enrique Medina.
_________________________________________________________________
Descarga gratis la Barra de Herramientas de MSN http://www.msn.es/usuario/busqueda/barra?XAPID=2031&DI=1055&SU=http%3A//www.hotmail.com&HL=LINKTAG1OPENINGTEXT_MSNBH
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
