Then you do not need uuids at all. You can just db(query).select().export_to_csv_file(...) the records you want to export and db.table.import_from_csv_file(...) to import them back.
There is a recent thread on how import_from_sv_file handles and fixes references. Massimo On Dec 23, 4:19 am, seeker <[email protected]> wrote: > Thanks Massimo. Great/useful example (for certain use cases). > > Your example, at last, made me realize that we have made (I think...) > slightly different assumptions in the discussion of this issue thus > far: > > In my case I am simply trying to aggregate multiple child databases > into one parent database. In other words the records in the child > databases are newly created there and then later uploaded to the > parent. Maybe an example will clarify: > > 1] a number of records are created in ChildDB_A and then uploaded to > ParentDB. > 2] a number of OTHER records are created in ChildDB_B and then > uploaded to ParentDB. > > In step 2 I do not wish to update the records previously inserted in > step 1; I simply wish to add more (different) records to ParentDB. > If I were to use standard integer id's though there will be a good > chance that the id's from step 1 and step 2 will overlap (and cause > chaos). > > Hope that clarifies my problem (or highlights my lack of > understanding ;-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
