Thread: [SQLObject] caching objects found by alt IDs
SQLObject is a Python ORM.
Brought to you by:
ianbicking,
phd
From: Garrett S. <ga...@mo...> - 2006-02-05 02:44:34
|
I was surprised to see that object looked by alt ID results in a query for = each lookup. Objects read via get (primary key) are cached. Has there been = any discussion about fixing this? If it's generally agreed that this would be appropriate, I can add a SF bug= /feature request. Garrett |
From: Oleg B. <ph...@ma...> - 2006-02-05 19:21:47
|
On Sat, Feb 04, 2006 at 08:50:00PM -0600, Garrett Smith wrote: > I was surprised to see that object looked by alt ID results in a query > for each lookup. Objects read via get (primary key) are cached. Has there > been any discussion about fixing this? > > If it's generally agreed that this would be appropriate, I can add a SF > bug/feature request. If possible add also a test case. Oleg. -- Oleg Broytmann http://phd.pp.ru/ ph...@ph... Programmers don't die, they just GOSUB without RETURN. |
From: Ian B. <ia...@co...> - 2006-02-07 02:18:49
|
Garrett Smith wrote: > I was surprised to see that object looked by alt ID results in a > query for each lookup. Objects read via get (primary key) are cached. > Has there been any discussion about fixing this? alternateID columns aren't immutable like primary key columns are, which is why the lookup isn't cached. I think any caching of alternateIDs needs to be explicitly enabled in the column definition. -- Ian Bicking | ia...@co... | http://blog.ianbicking.org |