I need to take an existing db and implement a UUID referencing system so that I can sync local db's with a central remote version. But I'm concerned that this will break reference fields that refer to the newly synced rows.
My understanding is that the UUID field is necessary because a csv import will assign different row ids to the new entries in the target db than the ones they had in the source db (especially if new records have been added to the target db in the meantime). The UUID is supposed to overcome this, by allowing the db to recognize that rows are equivalent even if they have different ids. But in that case, won't reference fields in other tables often be pointing to the wrong ID number in the target db? (i.e., they'll keep the row ID of the db version in which they were created, and if this ID changes in the target db they will then be referencing a different record.) Sorry if this explanation is overly complicated. I'm just trying to get things clear in my own mind. Thanks -- 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.
