You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I cannot edit any column value when table has a composite key and a JSON column
To Reproduce
Steps to reproduce the behavior:
Create the following table:
CREATE TABLE `tmp_bug_antares` (
`product_id` char(36) CHARACTER SET utf8mb3 COLLATE utf8mb3_unicode_ci NOT NULL,
`category_id` char(36) CHARACTER SET utf8mb3 COLLATE utf8mb3_unicode_ci NOT NULL,
`status` varchar(255) CHARACTER SET utf8mb3 COLLATE utf8mb3_unicode_ci NOT NULL,
`images` json NOT NULL,
PRIMARY KEY (`product_id`,`category_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb3 COLLATE=utf8mb3_unicode_ci
Insert a record
INSERT INTO `tmp_bug_antares` (`product_id`, `category_id`, `status`, `images`) VALUES ("18ff3cc2-4ee9-4fc0-ade2-d2b9b5ee6120","8b3431fd-8663-4180-9f1d-91553484ec09","test","[]");
Try to edit any field
Error is displayed and changes are not applied ("You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'LIMIT 1' at line 1")
Expected behavior
Field is updated with value typed
This might be a bit related to my PR #919 . We need to encode to json first. @Fabio286, are you currently working on it? If not, would it be okay for me to take a shot at fixing it?
This might be a bit related to my PR #919 . We need to encode to json first. @Fabio286, are you currently working on it? If not, would it be okay for me to take a shot at fixing it?
Hi @dyaskur, I haven't started working on it yet.
If it's not a problem for you to try to fix I would be very grateful!
Describe the bug
I cannot edit any column value when table has a composite key and a JSON column
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Field is updated with value typed
Screenshots
https://github.com/user-attachments/assets/d688d6d7-6229-4c5b-91a3-145a9b3feca8
Application:
Environment:
Additional context
Works fin if JSON column is removed or if there is only a single primary key column
The text was updated successfully, but these errors were encountered: