If you want to avoid duplicate associations, check out
update_or_insert.

http://web2py.com/books/default/chapter/29/6#update_or_insert

In raw SQL you would use the two associated IDs as the primary key,
then use ON DUPLICATE KEY to trap the error.

On Feb 16, 8:09 am, Ross Peoples <ross.peop...@gmail.com> wrote:
> Good practice says you should ALWAYS have an identity (ID) field, even if
> you don't use it.

Reply via email to