Consider dropping SQLite.jl APIs entirely in favor of DBInterface.jl

Open jeremiahpslewis opened this issue 3 years ago • 3 comments

It seems like there are a number of errors / user challenges which arise as a result of the overlapping / intersecting API domains. It might make sense (as part of a breaking change release) to drop the 'custom' SQLite interface as much as possible in favor of the generic DBInterface onee.

https://github.com/JuliaDatabases/SQLite.jl/issues/283
https://github.com/JuliaDatabases/SQLite.jl/issues/278

Feb 01 '22 15:02 jeremiahpslewis

Yeah; I'm in favor. Up for making a PR @jeremiahpslewis ?

Feb 02 '22 04:02 quinnj

Happy to do this if I get a chance, I'd break it up into 2 PRs:

Remove all overlapping SQLite -DBInterface tests
Remove / deprecate all overlapping code

Feb 02 '22 09:02 jeremiahpslewis

That sounds like a great plan @jeremiahpslewis!

Feb 11 '22 22:02 quinnj