What would this support look like? How would the sequence be
specified, and how would it behave on insert, update, etc.?
I suppose my use of serial/sequence columns is too specific to bother adding
to the API, but basically
some_seq_column => { type => 'serial', not_null => 1, sequence => 'some_seq'
},
would use nextval('some_seq') on save if that column is missing. Similar to
the primary key generation that happens already.
But since next_value_in_sequence is not documented, I am worrying that
it's
> interface may change or disappear.
It almost certainly won't disappear and may become part of the public
API eventually.
Fantastic-- that's really all I need. Thanks for all the great work.
Derek
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Rose-db-object mailing list
Rose-db-object@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rose-db-object
