AUTOINCREMENT primary keys

BugsBiteBugs / sqlitepersistentobjects

Automatically exported from code.google.com/p/sqlitepersistentobjects

0 stars 0 forks source link

AUTOINCREMENT primary keys #46

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

I asked this on the google group[1].  The AUTOINCREMENT approach makes
sense to me, but maybe there are some sqlite gurus who can weigh in.

[1]
http://groups.google.com/group/sqlitepersistentobjects-user/browse_thread/thread
/5110d82e70912446#

Original issue reported on code.google.com by li...@wzph.com on 21 Feb 2009 at 6:44

GoogleCodeExporter commented 9 years ago

I will have a play with using this and if it looks ok will apply it.

Original comment by chris.go...@kimptoc.net on 21 Feb 2009 at 12:10

Changed state: Started

GoogleCodeExporter commented 9 years ago

I've checked in an alternative implementation of AUTOINCREMENT to  r106. 

The SQLite default version looks harder to implement because you only get to 
see what
the new object's pk value is at the very end of the save block, we currently 
need it
at the start to save the xRef collection properties

Original comment by amle...@gmail.com on 22 Feb 2009 at 5:29

GoogleCodeExporter commented 9 years ago

Cool, makes sense - I have re-assigned this item to you, hope thats ok.

Original comment by chris.go...@kimptoc.net on 22 Feb 2009 at 7:53