MariaDBFormPersistenceService draft delete generates SQL that MariaDB 10.6 rejects #69

New issue

Open

opened 2026-10-04 12:09:16 +00:00 by claude · 0 comments

claude commented

2026-10-04 12:09:16 +00:00

Member

Support-lib MariaDBFormPersistenceService.put(key)(None) (draft delete) generates SQL that MariaDB 10.6 rejects (DELETE x11 WHERE ..., syntax error), so the draft delete endpoint formsPersistence.delete may fail against MariaDB. Not investigated further; FormsLoadDescriptorOnlyIntegrationSpec deletes its drafts with plain JDBC because of it.

MEDECA-632's FormsLoadDescriptorOnlyIntegrationSpec (medeca-modul-poptavky) works around it: it deletes its drafts with plain JDBC instead of MariaDBFormPersistenceService.put(key)(None).

Source: the FOLLOW-UPS.md of MEDECA-632 (project-management/issues/MEDECA-632/FOLLOW-UPS.md in medeca-modul-poptavky).

- Support-lib `MariaDBFormPersistenceService.put(key)(None)` (draft delete) generates SQL that MariaDB 10.6 rejects (`DELETE x11 WHERE ...`, syntax error), so the draft delete endpoint `formsPersistence.delete` may fail against MariaDB. Not investigated further; `FormsLoadDescriptorOnlyIntegrationSpec` deletes its drafts with plain JDBC because of it. MEDECA-632's `FormsLoadDescriptorOnlyIntegrationSpec` (medeca-modul-poptavky) works around it: it deletes its drafts with plain JDBC instead of `MariaDBFormPersistenceService.put(key)(None)`. Source: the FOLLOW-UPS.md of MEDECA-632 (`project-management/issues/MEDECA-632/FOLLOW-UPS.md` in medeca-modul-poptavky).