many other
relationships defined to other lookup tables that are modeled
identically and do not exhibit any circular dependency problems.
On Sep 24, 10:49 am, Randallabra <[EMAIL PROTECTED]> wrote:
> There is a case in my application where setting the attribute
> 'version&#
There is a case in my application where setting the attribute
'version' which is the name of a relationship to a look up table. When
I avoid setting this attribute, saving the record takes 0.15s, however
when I set the value of this relationship, saving the record takes
upwards of 30 seconds.
Fur
Awesome! Thank you very much indeed for the follow-up.
After turning of expire_on_commit, saving a newly created object takes
less than 1/3 of a second even with 100K objects in memory.
It's always nice to find the "fast = True" switch. :-)
On Sep 23, 6:00 pm, Michael Bayer <[EMAIL PROTECTED]>
Here is the scenario. I'm using SA as the data abstraction/access
layer between a desktop application and postgresql database. The user
interacts with the application primarily by browsing large numbers of
records (on the order of tens of thousands of records at once).
Occasionally the users needs
