Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:
The old API defined a unique field as follows:
_sql_constraints = [
('cne_unique', 'unique(cne)', 'cne already exists!')
]
The new API deprecates this, and recommends to use @api.constrains, but how can I code to check for uniqueness in an efficient way?
Hi
this is _constraints which is deprecated (python constraint), not _sql_constraints, see :
@Cyril: please read my question. I know it is deprecated, I need to know how to do this in v8.
please read my answer and verify in link I gave, _constraints and and _sql_constraints are two different things, you talk about _sql_constraints and this is not deprecated, see after => copy/paste v8 doc (link I gave) : _constraints list of (constraint_function, message, fields) defining Python constraints. The fields list is indicative Deprecated since version 8.0: use constrains() _sql_constraints list of (name, sql_definition, message) triples defining SQL constraints to execute when generating the backing table
Cyril, I sincerely apologize. You were completely right. _sql_constraints is not deprecated. I just don't know how to read. Thanks.
Now you have your answer ^^, bye
Luo tili jo tänään nauttiaksesi yksinoikeusominaisuuksista ja osallistuaksesi mahtavaan yhteisöömme!
Rekisteröidy| Aiheeseen liittyviä artikkeleita | Vastaukset | Näkymät | Toimenpide | |
|---|---|---|---|---|
|
1
marrask. 22
|
3318 | ||
|
0
kesäk. 21
|
5860 | ||
|
0
maalisk. 21
|
2718 | ||
|
2
tammik. 20
|
21586 | ||
|
2
toukok. 18
|
3999 |
1. Use the live chat to ask your questions.
2. The operator answers within a few minutes.
