Replies: 1 comment 1 reply
-
It seems feasible to add TiDB as a separate dialect and use a switch where needed. Note that we have supported TiDB in the past: photoprism/internal/config/config_db.go Line 46 in 240393d There just wasn't enough time to maintain it, and there hasn't been much demand for it either. So if we were to reintroduce TiDB support, this would require ongoing help with maintenance and testing. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there. I'm Dan, a software/data engineer / DBA, currently working as a support engineer / DBA / TAM for PingCAP, the authors of TiDB. As I already run a bunch of TiDB clusters ( including on my home server, where I'm setting up photoprism ), it makes sense for me to put everything MySQL-compatible into it, and generally play around with it, trying to break things.
As such, I've attempted to bring up Photoprism on TiDB, and hit some small issues ( eg ticket #3199 and ticket #3216 ... which I submitted a patch for in #3217 ). I see there are a few more issues, like "create or replace" syntax for indexes that don't parse on TiDB ( the "or replace" part isn't parsed ), and things that could be worked around by setting a SQL_MODE session variable upon connecting ( eg no_zero_in_date ).
I assume there would only be a small number of further fixes until it's working. I'm interested in completing this, and wondering:
Beta Was this translation helpful? Give feedback.
All reactions