On Dec 22, 2009, at 2:51 PM, Igor Katson wrote: > > I am concerned about the problem of the orm framework using SELECT's a > lot, which can be not used in many cases, when dealing with Postgres > after INSERTs or UPDATEs.
on this point specifically, when a SQL expression is used to generate the value of a new column, no SELECT occurs to fetch that value unless you specifically request it (unless you're using an extremely old version of SQLA). So there's no concern for many unnecessary SELECT statements being invoked. Additionally, after a commit(), the objects are expired (again this is optional but recommended behavior), but again no SELECT occurs unless you access the expired object's attributes. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
