1. eDBI and SQLite
- Posted by jeremy (admin) Sep 12, 2009
- 1358 views
Forked from Re: Bug or Error
Hi
Then you'd still be better of using a database system that could handle BLOBs - I know sqlite can, but haven't got around to adding it to the wrappers yet, as I simply haven't needed it.
Chris, have you looked at eDBI any? I include a SQLite driver so eDBI can access SQLite files. It's written in C and it compiles right in the sqlite3.c file so you don't need a sqlite.so/dll.
It also, does not support blob's at this point. I'd be curious for your input.
http://jeremy.cowgar.com/svn/edbi/trunk
You can run eudoc edbi/edbi.e to get basic docs on it, or read the source. They are helpful but not yet complete.
Jeremy
2. Re: eDBI and SQLite
- Posted by ChrisB (moderator) Sep 13, 2009
- 1287 views
Hi
Sorry, I didn't notice this, I'll certainly look at them.
Chris
3. Re: eDBI and SQLite
- Posted by ChrisB (moderator) Sep 13, 2009
- 1241 views
- Last edited Sep 14, 2009
Hi
This is technically v nice, and I can see the advantage of having a unified database front end. My only niggle with this system is that the lowest common denominator has to be accommodated. I can't think of any specific examples, but there are some API functions present in sqlite, not present in the others, and some SQL is not supported in sqlite that is supported in the others, and could lead to misunderstandings in production code.
I am unlikely to switch to MySQL or PostgreSQL in the near future (although its not totally impossible), and this is a worthwhile project, but its fairly unlikey that I'm going to be able to add anything useful to what you are doing (or as prolifically as you do)
Chris
4. Re: eDBI and SQLite
- Posted by jeremy (admin) Sep 13, 2009
- 1238 views
- Last edited Sep 14, 2009
This is technically v nice, and I can see the advantage of having a unified database front end. My only niggle with this system is that the lowest common denominator has to be accommodated. I can't think of any specific examples, but there are some API functions present in sqlite, not present in the others, and some SQL is not supported in sqlite that is supported in the others, and could lead to misunderstandings in production code.
Yes, this is always the problem with a cross-db interface.
I am unlikely to switch to MySQL or PostgreSQL in the near future (although its not totally impossible), and this is a worthwhile project, but its fairly unlikey that I'm going to be able to add anything useful to what you are doing (or as prolifically as you do)
If the application in question does not plan to nor benefit from multiple databases, then I would use a native database library as well, and do with PostgreSQL.
Jeremy
5. Re: eDBI and SQLite
- Posted by DerekParnell (admin) Sep 13, 2009
- 1299 views
- Last edited Sep 14, 2009
I am unlikely to switch to MySQL or PostgreSQL in the near future (although its not totally impossible), and this is a worthwhile project, but its fairly unlikey that I'm going to be able to add anything useful to what you are doing (or as prolifically as you do)
If the application in question does not plan to nor benefit from multiple databases, then I would use a native database library as well, and do with PostgreSQL.
I can think of a number of instances when talking to a potential customer, and they say "But does it also run on 'xxx' because that's our corporate database standard and we are not going to hire or train someone to use anything else."
So our products had to be capable of being ported to 'foreign' databases with the minimum of effort.
