This should now be fixed in trunk. Please check it. On Thursday, 6 June 2013 08:19:35 UTC-5, Lamps902 wrote: > > To clarify, due to the SQL Foreign Key constraint (which is retained when > archive tables are created through auth.enable_record_versioning), some of > the archive database's tables still retain an association with the > auth_user table's id field. However, the rows with the ids on which the new > tables depend may not necessarily be transferred from the application's > primary database to the archive database. Is there a way to use the DAL to > remove the Foreign Key constraint? Thanks. >
-- --- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
