typically you want to do an objectstore.clear() at the start of every
request.the commit(), maybe, if youve architected that way, i
would imagine youd want to do it before your view fires
offneither incurs any kind of performance overhead if theres
nothing to be saved.
On Mar 8,
Michael Bayer wrote:
well from a dependency point of view these two dumps are identical, so
its not a bad dependency sort (whew).
Yeah. I'm very happy it's not an SA problem.
In the bad version, you have two separate instances of a Timesheet
object (those numbers in the parenthesis are the Py
well from a dependency point of view these two dumps are identical, so its not a bad dependency sort (whew).In the bad version, you have two separate instances of a Timesheet object (those numbers in the parenthesis are the Python id() of the object). Id make a random guess that one of them is mis
Michael Bayer wrote:
its definitely not a threading prob within SA. could be a "dirty
flag" type of thing. or it is conceivable that your dependencies are
not being set properly when you are committing; I have noticed on a
surprisingly enormous number of occasions that printing out data
aff
its definitely not a threading prob within SA. could be a "dirty
flag" type of thing. or it is conceivable that your dependencies
are not being set properly when you are committing; I have noticed on
a surprisingly enormous number of occasions that printing out data
affects the way dicti
Hi,
I am using sqlalchemy with pylons. I have a very simple table with a
foreign key to another table.
I pretty much submit a form load the values into the object and use
objectstore.commit() to save the record.
Once in a while I get a strange error where it complains that the
foreign key
6 matches
Mail list logo
