Repairing the table definition didn't help. I'm now going to try the operations on a fresh table.
On Thursday, March 26, 2015 at 10:42:33 AM UTC-4, Ian W. Scott wrote: > > Thanks Niphlod. I hired someone to migrate the db from sqlite to postgre > and there seem to be some bugs in the migration. I hadn't noticed the lack > of reference fields because they were originally there. I think the guy I > hired must have removed them (?!). I'll try repairing the table definition > first. > > The unique constraint, though, is on the db index not on the table fields, > right? > > On Wednesday, March 25, 2015 at 6:42:10 PM UTC-4, Niphlod wrote: >> >> apart from the repetitive table definition (why reinstating IS_IN_DB when >> you can do it simply using 'reference table' instead of db.table ?).... >> >> did you try creating the same table from scratch ? i.e. a tag_records2 >> table, which you can try your things on. >> >> It seems that there is a unique constraint on the table, but your model >> isn't reflecting that enforcement. Maybe you had some migration issues. >> >> >> -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
