On Mar 11, 9:56 am, mdipierro <[email protected]> wrote: > Should the record id be assigned by the DB or by the user? I > think it should be assigned by the DB. The practical issue is that > SQLFORM assumes the current record id. You change that and everything > break. It can be fixed but web2py will become much more bloated. I > believe having an autoincrement id should be considered good practice > and enforced by web2py.
Record id is just a convenience, you can get to a specific record using its primary key(s) and that is how most tables are normally built. So, e.g. the ISBN number can be a primary key in a books DB and there is not much difference (unless I am failing to see something) between using it or using an extra id field. When the primary key consists of several fields the id-ing can be done using a list. I honestly don't know how much bloating can this produce. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
