[Twisted-Python] enterprise.row

Dave Peticolas dave at krondo.com
Mon Apr 7 16:17:46 EDT 2003

On Mon, 2003-04-07 at 06:43, Justin Ryan wrote:
> > > I don't really see how allowing key columns to be ignored on an insert
> > > would be database specific..  Ideally, whether or not a default value is
> > 
> > I don't think I fully articulated my thoughts. Currently the 'reflector'
> > code caches the rows you create. So, ideally, if the database is going
> > to set default values on a new row, you'd like the reflector to update
> > the row object with whatever values the database chose to maintain
> > consistency between the row object and the database. I haven't
> > thought about it too closely, but it seems to me that there's no
> > way to implement that in a database-independent way, but maybe I'm
> > just missing something.
> > 
> > What do you think?
> Welll...
> I think that if you insert a row and allow the database to assign the
> pkey, you can select out the pkey.  I'm not sure this is more efficient
> than selecting nextval() before insert, but it would be more
> database-independent..

That would only work if twisted is the only process adding rows,
I think.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://twistedmatrix.com/pipermail/twisted-python/attachments/20030407/9af5cb07/attachment.pgp 

More information about the Twisted-Python mailing list