Tryton - Issues



Title Remove unique constraint on sepa identifier
Priority feature Status resolved
Superseder Nosy List ced, reviewbot, roundup-bot
Type feature request Components account_payment_sepa
Assigned To ced Keywords review
Reviews 64511002
View: 64511002

Created on 2018-12-20.15:57:39 by ced, last changed by roundup-bot.

New changeset f582aa9f8628 by Cédric Krier in branch 'default':
Remove unique check on SEPA identifier
New changeset 6c1d45327fda by Cédric Krier in branch 'default':
Remove unique check on SEPA identifier
review64511002 updated at
msg45411 (view) Author: [hidden] (ced) (Tryton committer) (Tryton translator) Date: 2018-12-20.15:57:38
Even if normally there should be only one sepa identifier per party, it is not really necessary to have such constraint. The identifier are ordered so we take as usual the first one.
Also the current constraint is even not concurrent safe.
Date User Action Args
2018-12-22 17:43:35roundup-botsetmessages: + msg45472
2018-12-22 17:43:31roundup-botsetstatus: testing -> resolved
nosy: + roundup-bot
messages: + msg45471
2018-12-20 16:15:09reviewbotsetnosy: + reviewbot
messages: + msg45412
2018-12-20 15:59:09cedlinkissue3672 superseder
2018-12-20 15:59:00cedsetstatus: in-progress -> testing
reviews: 64511002
keyword: + review
2018-12-20 15:57:39cedcreate