SQLite limitations still in effect?

[brandonzylstra]

Supported databases are PostgreSQL and MySQL. Note: Unfortunately, SQLite raises a poor error message by which we can not determine exact foreign key which raised an error.

SQLite has gotten a lot of attention in the last years and the whole ecosystem has improved a lot. I would not be surprised if SQLite itself has improved their error messages. Is it possible to lift this limitation?

Or has this gem been abandoned?

[djezzzl]

Hi @brandonzylstra,

I have to check whether it's possible now with SQLite.

Unfortunately, I don't have much time recently, but I see I'm still part of the owners of the gem, so I might try to apply changes and publish the gem. However, I am not part of the Github repo owners, so it could be it won't be merged.

Do you have time and opportunity to check this support?

[djezzzl]

Hi @bbatsov @paneq 👋 ,

Is it possible to give me an admin rights in this repo so I don't bother you with help requests? It could stay under Toptal, yet transfer is also possible and appreciated.

Thank you!

[brandonzylstra]

Do you have time and opportunity to check this support?

I'm not sure where to begin. I don't know what error message is in question here, so I don't know where I would look in the SQLite documentation. I could start with an LLM but I wouldn't have enough background knowledge to know whether it is hallucinating or not.

[djezzzl]

I think there is a spec that you can uncomment (or remove if statement) for SQLite. Then, you will see an error message and it will be obvious to understand if the message is enough to properly map to a validation.