Hey Franciszek, Franciszek Stachura, Sep 19, 2026 at 01:05: > I'm wondering, is MySQL support planned for patchwork-next? It seems to > me that patchwork-next does not work with MySQL at all, despite the > documentation suggesting that it does. I gave implementing it a shot, > but there are a couple of problems: > - Text fields default to VARCHAR(255). Index key length has to be > specified for the unlimited TEXT type. bun does not support that in > the model field tags. So changing unique/indexed fields to the TEXT > type requires creating the indexes manually. > - RETURNING is not supported > - CONFLICT targets are not supported
I must admit, I haven't tested on MySQL. I tried to make it as close as possible but obviously missed a few spots :( > To be fair, while working with Patchwork I thought that it would be > pretty convenient to support only a single database. > patchwork-next requires a migration either way. > On the other hand, I'm not sure if projects that use Patchwork right > now would be happy if MySQL support was dropped from 4.x. > Migrating a small database may be easy, but having to set up a larger > cluster again... I would also be in favor of dropping MySQL. I always found this DB engine worse than Postgres in all aspects (reliability, performance, ease of use, tooling, etc.). To be honest, I really hope that nobody is running large installations with MySQL and setting up Postgres on a single host is really straightforward. Would anyone be opposed to Patchwork 4.x dropping MySQL and only supporting Postgres for production (and SQLite for testing and development)? -- Robin # No motorized vehicles allowed. _______________________________________________ Patchwork mailing list [email protected] https://lists.ozlabs.org/listinfo/patchwork
