Thank you for that, I didn't realize I needed to drop the tables. It is
working exactly as expected now.
On Tuesday, December 17, 2013 8:08:06 PM UTC-7, Massimo Di Pierro wrote:
The problem is that my workaround is not retroactive. I believe the bug is
fixed but does not apply to tables
Running version 2.8.2-stable+timestamp.2013.11.28.13.54.07 I recieved the
same error as described above. I also tried to use the workaround Massimo
suggested below, but without success, the update still fails. Do I need to
delete my current archive table before attempting this?
On Monday,
The problem is that my workaround is not retroactive. I believe the bug is
fixed but does not apply to tables created before the upgrade with the
fixed code.
You have to manually alter table and remove the UNIQUE attribute. web2py is
not smart enough to be able to do that.
On Tuesday, 17
Hi Massimo,
Thanks for your (quick) answer! I've created an issue for this:
http://code.google.com/p/web2py/issues/detail?id=900
I'll try to implement the modern approach and the 'requires work-around'
Remco
On Tuesday, July 17, 2012 4:03:20 AM UTC+2, Massimo Di Pierro wrote:
For the time
This is a bug. The archive function creates a an auxiliary table to store
copies of the current record.
It reproduces the same table structure as your table including
(incorrectly) the unique attribute.
This fails when you insert ore than one revision.
Please open a ticket on google code.
For the time being... remove unique=True and use
requires=(IS_EMAIL(),IS_NOT_IN_DB(db,'auth_user.email'))
On Monday, July 16, 2012 9:01:54 PM UTC-5, Massimo Di Pierro wrote:
This is a bug. The archive function creates a an auxiliary table to store
copies of the current record.
It
6 matches
Mail list logo
