You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 30, 2021. It is now read-only.
Initial point of discussion is what model to base a potential new database standard interface on. Examples include this package, existing interfaces for ODBC and LibPQ. Another intriguing possibility is embracing DataKnots.jl as a standard.
Here is a list of goals we should consider:
A simple, uniform interface across all Julia database packages that allows users to query with any SQL string and dump into any DataStreams Sink.
An unobtrusive design that makes it easy for users to use special features of individual packages that may not be universal (this is the one place where, if we are very careful, we might be able to offer something that sqlalchemy can’t).
Simple for package maintainers to implement (at least the minimum features).
Some level of compatibility with Spark, or at least carefully checking that this is feasible.
A path toward ORM.
The text was updated successfully, but these errors were encountered:
I'm on-board for finally solving this problem in its smallest form, i.e. mimicking what R/Python/Perl have accomplished with DBI. After that, people can feel free to start making ORMs or whatever that fits their taste as other packages.
Continuing discussion in this thread.
Initial point of discussion is what model to base a potential new database standard interface on. Examples include this package, existing interfaces for ODBC and LibPQ. Another intriguing possibility is embracing DataKnots.jl as a standard.
Here is a list of goals we should consider:
The text was updated successfully, but these errors were encountered: