Adrien de Peretti
da3906efa4
FIXES FRMW-2878 **What** Currently, the `one-to-one` unique constraints does not account for deleted record. This prevents from inserting a new record wth the same fk if another one is deleted. **Caveat** `hasOne` with FK option is meant to be a special case, for example a many to one - one to many without defining the other side of the relation. In that case we don't handle this behaviour and keep it as it is
385 B
385 B
@medusajs/cart, @medusajs/fulfillment, @medusajs/notification, @medusajs/payment, @medusajs/promotion, @medusajs/region, @medusajs/stock-location, @medusajs/workflow-engine-inmemory, @medusajs/workflow-engine-redis, @medusajs/utils
| @medusajs/cart | @medusajs/fulfillment | @medusajs/notification | @medusajs/payment | @medusajs/promotion | @medusajs/region | @medusajs/stock-location | @medusajs/workflow-engine-inmemory | @medusajs/workflow-engine-redis | @medusajs/utils |
|---|---|---|---|---|---|---|---|---|---|
| patch | patch | patch | patch | patch | patch | patch | patch | patch | patch |
fix: Unique constraint should account for soft deleted records