Jim Gallacher wrote:
Using bsddb3 would introduce new dependency for mod_python, so I don't
know if it's a good idea to use transaction handling by default for
DbmSession. Maybe we could offer a subclass?
Starting with Python 2.3 this module is included in the standard python
distribution as
Nick wrote:
Jim Gallacher wrote:
Using bsddb3 would introduce new dependency for mod_python, so I don't
know if it's a good idea to use transaction handling by default for
DbmSession. Maybe we could offer a subclass?
Starting with Python 2.3 this module is included in the standard python
Nick wrote:
Jim Gallacher wrote:
Nick wrote:
Jim Gallacher wrote:
Using bsddb3 would introduce new dependency for mod_python, so I
don't know if it's a good idea to use transaction handling by
default for DbmSession. Maybe we could offer a subclass?
Starting with Python 2.3 this
On Fri, 17 Jun 2005, Nicolas Lehuen wrote:
As for the MySQL implementation
I'd stay away from anything vendor-specific in mod_python, because then
the question becomes why not a postresql, why not oracle, etc.
Grisha
Gregory (Grisha) Trubetskoy wrote:
On Fri, 17 Jun 2005, Jim Gallacher wrote:
I was thinking we'd still use the current global locking scheme, but
keep the file open between requests. Not sure if this would be robust
or just asking for dbm file corruption though.
I'm pretty sure it won't
Gregory (Grisha) Trubetskoy wrote:
On Fri, 17 Jun 2005, Jim Gallacher wrote:
Any objection to just a SqlSession base class?
May be - it depends on how complex it becomes. Any attempts I've to
generalize SQL/DB stuff tend to become a mess since there are no firm
standards in this area,
