Jonathan Ellis wrote:
On 5/9/06, *Luís Bruno* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Huy Do wrote:
> I always do a session.clear() after I do my stored procs/triggers.
Which just reminded me of PostgreSQL notifications. Maybe watching for
those and reload the objects specified by the trigger in the
notification message (or just invalidate part of the cache) would be a
nice idea.
Notifications are inherently not transaction-safe, besides being
pg-specific. Not worth it IMO.
--
Jonathan Ellis
http://spyced.blogspot.com
I agree. Lets keep the ORM as simple as possible. We don't want to get
too lazy ;-)
Can I ask how many people actually find the cache useful ? I find it
tends to hinder me more then be useful.
I tend to keep my own references to objects (i.e pass as parameters or
local reference) when I need to refer to the same object again. When I
do Object.get() or Object.select(), I tend to want the fresh data from
the database. I memoize any other selects which I know don't need to hit
the db.
Is there a switch/config option in SA to always hit the DB when we call
a query method ?
Regards,
Huy
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
_______________________________________________
Sqlalchemy-users mailing list
Sqlalchemy-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
