Error updating 1.3.1 to 1.3.2 in docker #210

New Issue

OVERLORD · 2026-02-04T17:51:17+03:00

OVERLORD commented

2026-02-04 17:51:17 +03:00

Originally created by @pztrn on GitHub (Jun 24, 2022).

planka_1  | Warning: Adapter sent back a uniqueness error, but that error references key(s) (card_id, user_id) which cannot
planka_1  | be matched up with the column names of any attributes in this model (`cardsubscription`).  This probably
planka_1  | means there is a bug in this adapter.
planka_1  | (Note for adapter implementors: If your adapter doesn't support granular reporting of the keys violated
planka_1  | in uniqueness errors, then just use an empty array for the `keys` property of this error.)
planka_1  | (Proceeding anyway as if these keys weren't included...)

And that's it. Search gives me nothing in issues.

Originally created by @pztrn on GitHub (Jun 24, 2022). ``` planka_1 | Warning: Adapter sent back a uniqueness error, but that error references key(s) (card_id, user_id) which cannot planka_1 | be matched up with the column names of any attributes in this model (`cardsubscription`). This probably planka_1 | means there is a bug in this adapter. planka_1 | (Note for adapter implementors: If your adapter doesn't support granular reporting of the keys violated planka_1 | in uniqueness errors, then just use an empty array for the `keys` property of this error.) planka_1 | (Proceeding anyway as if these keys weren't included...) ``` And that's it. Search gives me nothing in issues.

OVERLORD closed this issue

2026-02-04 17:51:23 +03:00

OVERLORD commented

2026-02-04 17:51:26 +03:00

@meltyshev commented on GitHub (Aug 1, 2022):

Hi! It seems to be just a warning because the database adapter can't handle uniqueness constraint for composite index. So these warnings can be skipped.

Related issue: https://github.com/balderdashy/sails/issues/4632.

@meltyshev commented on GitHub (Aug 1, 2022): Hi! It seems to be just a warning because the database adapter can't handle uniqueness constraint for composite index. So these warnings can be skipped. Related issue: https://github.com/balderdashy/sails/issues/4632.

OVERLORD referenced this issue

2026-02-04 21:40:35 +03:00

[PR #210] [CLOSED] Bump node-forge from 1.2.1 to 1.3.0 in /client #956

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/planka#210