Hello!
My company uses SQLObject solely for desktop applications.
On Sun, Feb 01, 2009 at 03:49:46PM -0500, Stef Telford wrote:
> *) There is writeLocks - surely not required since most frameworks
> run the entire thread under a transaction anyway.
I don't see how a web transaction is related to multithread-safe locks.
Whatever a web transaction is, there are a lot of different web frameworks,
and who guarantees it is thread-safe to touch shared variables?
> *) cache built in at a fundamental level - most web people would
> probably feel safer with memcache, currently I don't see anyway to
> disable this
Probably by writing a Cache class that doesn't cache.
> *) no query caching
What is a query in terms of an ORM? If 'document' is an SQLObject,
attribute access like 'document.title' is implemented using a SQL query.
How does query caching help?
In any case - if query caching helps, SQLObject will benefit if somebody
commits a code, right?
> *) connection pooling - I would have thought (again perhaps
> naively) that in a web environment, this should exist outside the ORM.
It is easy to disable: connection._pool = None.
> So, is it insanity to propose that perhaps there is a
> sqlobject-web version?
You are welcome to support one.
Oleg.
--
Oleg Broytmann http://phd.pp.ru/ [email protected]
Programmers don't die, they just GOSUB without RETURN.
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
sqlobject-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
