Proposal Unique (PhysObj.code, PhysObj.type) Constraint defined per PhysObj.Type

[petrus-v]

Hi there !

I'd like to propose a new constraint to ensure phyobj.code are unique for given physobj.type.

The idea would be to add a boolean field ensure_unique on PhysObj.Type to make it configurable. As I would suggest that AWB-core do not assume how PhysObj.code are used by developer, probably some developer use PhysObj.code field to collect lot number which require to allow duplicated code for this given PhysObj.Type

note: I've checked that PhysObj.code is nullable and (posgre)SQL consider Null as different value in this kind of unique constraint so even the ensure_unique is true that would let developers to unpack PhysObj with null value in a first step and assign the code afterwards in his workflow.

Does this is useful to share ? Can I create a PR to improve AWB-core directly or should I create a dedicated blok somewhere else ?

Regards,