[Twisted-Python] About adodb
Dave, thanks for your reply. the Python DB API. Other important database differences transparently handled by ADOdb include date-formating, associative arrays (records as dictionaries) and LOB-handling."
/Simon (STemplar)
On Fri, 2004-10-01 at 04:26, Simon wrote:
That sound useful. Does the python adodb implementation allow you to use datetime objects transparently?
So this would implement a super-set of the adbapi interface, then? I think this would probably be a useful addition.
db_row has already been mentioned on this list as a nice module. But wouldn't the associative array aspects of adodb eliminate the need for db_row? dave
Yep, functionwise it would be pretty much the same. db_row however has the advantage of using a different storage mechanism eliminating the need for a dictionary in each object (using __slots__). If you load a lot of objects that should be an advantage. My idea is to subclass db_row to add some data validation routines. Perhaps we could add some foreignkey functionality also to make it a worthy replacement of RowObject. /Simon
On Sat, 2004-10-02 at 02:35, Simon wrote:
That sounds like a good plan. An extension to adbapi to return db_row objects would be helpful too. There is a patch to do that now: http://www.twistedmatrix.com/users/roundup.twistd/twisted/issue632 But I think db_row is a better solution. Maybe you could post your code to that bug? thanks, dave
On Fri, 2004-10-01 at 04:26, Simon wrote:
That sound useful. Does the python adodb implementation allow you to use datetime objects transparently?
So this would implement a super-set of the adbapi interface, then? I think this would probably be a useful addition.
db_row has already been mentioned on this list as a nice module. But wouldn't the associative array aspects of adodb eliminate the need for db_row? dave
Yep, functionwise it would be pretty much the same. db_row however has the advantage of using a different storage mechanism eliminating the need for a dictionary in each object (using __slots__). If you load a lot of objects that should be an advantage. My idea is to subclass db_row to add some data validation routines. Perhaps we could add some foreignkey functionality also to make it a worthy replacement of RowObject. /Simon
On Sat, 2004-10-02 at 02:35, Simon wrote:
That sounds like a good plan. An extension to adbapi to return db_row objects would be helpful too. There is a patch to do that now: http://www.twistedmatrix.com/users/roundup.twistd/twisted/issue632 But I think db_row is a better solution. Maybe you could post your code to that bug? thanks, dave
participants (2)
-
Dave Peticolas -
Simon