-
Description:I have a Nova model, for which my use case requires a non-integer primary key (mysql: varchar). Detailed steps to reproduce the issue on a fresh Nova installation:I've created my database table using
in my migration. My entity class "Appointment" repeats this primary key column
, which works fine in the first place. I create an Action using the proposed way
and call it from my Appointment using
When I now try to run this action, this fails with the following database queue issue:
Proposal: The Nova queue database table should better use a varchar primary key to stay flexible. In most setups, the performance implication will be minor. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
See #4116 (comment) |
Beta Was this translation helpful? Give feedback.
See #4116 (comment)