Accessing an in-memory sqlite database via ODBC

Question

I have an in-memory database embedded in my application and I want other applications to be able access it via ODBC.

After searching for an hour, I think I have 2 options.

Write my own ODBC Driver which knows how to talk my application via the network.
Implement MySQL or Postgres wire protocol in my application so that the client application can use MySQL/Postgres drivers.

According to Creating a custom ODBC driver writing my own driver is a huge task and should not be taken lightly.

So here are my questions.

If I have to implement the wire protocol, am I correct in assuming that I can just create a thread which talks to database and communicates with the clients over the network? That sounds fairly simple to me.
Do you know of any reasons why I should choose one of MySQL/Postgres/Some other wire protocol over the others? My queries will be basic SELECT statements.
Is there any simpler way to access my in-memory sqlite DB via ODBC?

I'm new to the world of databases and would appreciate any pointers for further reading.

Have you tested [SQLite ODBC Driver](http://www.ch-werner.de/sqliteodbc/)? — Solarflare, Nov 25 '16 at 13:35
@Solarflare Yes, it only seems to work with a sqlite file on disk. I haven't gone through its source code to see how easy it is to extend it. — Bhargava Srinarasi, Nov 25 '16 at 13:38

score 1 · Accepted Answer · answered Nov 25 '16 at 10:38

1

You should create your own ODBC driver. Maybe you don't need to implement all ODBC functionality, and a subset will do.

Trying to emulate a different database with its quirks and idiosyncrasies will probably be more difficult.

answered Nov 25 '16 at 10:38

Laurenz Albe

I decided to write my own ODBC driver after considering the complexity of implementing the wire protocol. – Bhargava Srinarasi Nov 30 '16 at 11:02

1 Answers1