Ok - while not especially desirable, that's how sqlobject works.
Well say that I set cacheValues=True as the default. Is there a way I
can then *force* the next "Myclass.select()" (and dereferencing) to
cause a real db request, rather than using the cache? That is, is there
a recommended way in sqlobject to flush the cache?
Thanks!
David
Oleg Broytmann wrote:
On Fri, Apr 14, 2006 at 11:33:07PM -0400, David Geller wrote:
b. However, whenever you do something like rec.element, in order to
reference a single element from a previously obtained record, the system
will issue *another* db request to re-fetch the value for the column (in
this case, "element") for that record.
This is *not* what is desired.
This is how cacheValues=False works.
That is, if I fetch an entire record from a fresh db request, for
subsequent accessing of individual attributes of that record, I *do not*
want db requests to be made.
Then set cacheValues=True.
Oleg.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
sqlobject-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
