primary keys are primary keys. their only purpose is to be as small as possible while uniquely identifiyng a row, with the added bonus of being ordered. if you need strict sequential ordering, use another field.
On Wednesday, January 27, 2016 at 12:49:09 PM UTC+1, Pierre wrote: > > Hi everyone > > The default behaviour will result in irregular primary-key sequence like : > (1,2,3,6,7,8,12,13,14,20,23.......etc) > also It seems impossible to retrograde the 'automat-id-counter' like : > db.table.insert(id=5,field=value) eventhough there's no record with id=5 > so is it ok to let ondelete=cascade do its job or better to update-insert > deletable records ? > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
