Unique fields break table inclusion (inheritance) about web2py

[niphlod]

From [email protected] on February 07, 2012 09:20:46

can you send me a patch?

[niphlod]

From [email protected] on February 07, 2012 09:22:30

I see you posted the patch. thanks in the next issue.

Status: Duplicate

[niphlod]

From [email protected] on February 08, 2012 12:36:48

This is not a duplicate of 649.

The patch for #649 does not solve the default "requires" issue being wrong, as the form constraints have already been generated for the original (non existant table), and you need to put requires=[] on the original unique column or the sqlform / app admin has an exception when trying to validate inserted records.

I think the only way to really solve this issue is to copy the original "requires" of the field, and when copying a table, use the original requires (not the already set-up requires as is done now, which already has the wrong value), which will get expanded correctly. I would have done this patch, but it is in parts of the DAL I'm not yet feeling comfortable modifying -- I might do that in the next few weeks.

(Also, if that is being done, I suggest adding a "selfref" column type, which will expand to reference the current table, which is a cleaner solution than the current 649 patch, as it is never ambiguous -- but it only works if copying the original field type is done first, as is suggest in this issue)

[niphlod]

From [email protected] on March 12, 2012 13:05:46

Status: Accepted

[niphlod]

From [email protected] on September 11, 2012 14:33:43

Not sure if connected, but Unique does not work here (at least for Sqlite) ...

db.define_table('test', Field('name'), Field('person_id', 'reference person', unique=True))

In theory this would provide a constraint for a 1-1 relationship. Not a popular thing to do, but I guess it should still work, or documented that it doesn't.