Using this kind of technical keys (auto increment id, where autoincrement is provided by db) is quite common fo db-design. In fact re-using id's is more 'dangerous': normally the id is used in another table to make a reference. If for some reason not all related tables are maintained correctly (eg when the original row was deleted and a row referencing this row is not), data may end up being incorrectly joined.
So far no issues are reported regarding this. H On Mon, Jul 20, 2009 at 23:32, rb<[email protected]> wrote: > > The problem is, to be db agnostic I *have* to assume the worst. I > wonder if this don't-fill-in-the-id-holes holds true for SQLite and > postgres. > > --- > Rb > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" 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 -~----------~----~----~----~------~----~------~--~---
