Re: DBI for Euphoria
- Posted by jeremy (admin) Mar 15, 2009
- 952 views
This sort of thing would be great. The tough part is to avoid getting trapped by the lowest common denominator, while still having a rich and powerful interface.
Yes, this is hard for any DBI, yet they continue to thrive. In a lot of situations, a DBI interface will sacrifice some richness of the underlying database for the gain of working on any type of database. I am open to suggestions you may have to make that not the fait of a Euphoria based DBI, but I am unsure of how to avoid it totally.
I'd certainly be interested in using this for wxEDB. It currently uses ODBC for non-EDS databases. Basically, you can view data and execute queries. One potential downside to your proposed DBI would be the requirement to distribute multiple binaries.
Yes, distributing binaries is a problem. I am unsure of how to go about not distributing binaries but making the drivers dynamically loadable. I think dynamic loading is pretty important. For instance, I may not want to package my program including the source of every single database driver available. John Doe may never touch Firebird, ODBC, EDS or PgSQL, they are just going to use SQLite for development/personal installations and MySQL for network deploys.
I'm open to suggestions here as well.
Jeremy
