Re: Resources for building database *server* interface

The problem you have to communicate to the monks is your misconception what ODBC is. Essentially you ask for a server for the ODBC network protocol. But there is no such thing. ODBC is like DBI. You need an ODBC-Driver (aka DBD) for your Database to connect to it with ODBC. Happily(?) every(?) Database comes with an ODBC-Driver. It is installed when you install the Database. So you are not aware of this. Your hypothetical MetaDatabase would need its own ODBC-Driver. So essentially the question is:

How to write an ODBC-Driver in Perl?

Comment on Re: Resources for building database server interface

Replies are listed 'Best First'.
Re^2: Resources for building database server interface by simonm (Vicar) on Nov 12, 2004 at 21:14 UTC
Good point. From here: ODBC is a call-level interface, not an application, network layer, or database driver. So, if you want to use ODBC (which is probably what your existing clients are able to talk to), you'll need to build a Windows DLL and/or a Unix shared library that implements the ODBC driver calling interface, and turns that into some kind of network traffic to your virtual server. You could take a look at OpenLink's Multi-Tier product for a commercial example of this type of solution. (In fact, you might be able to decode the network protocol they're using, which would let you reuse the existing drivers they've compiled for various platforms.) There also seem to be some free solutions that you might be able to piggyback on, like Boeireep. Googling for "odbc driver generic network protocol" should find some more candidates.	[reply]
Re^2: Resources for building database server interface by etcshadow (Priest) on Nov 12, 2004 at 21:59 UTC
Good call. I'm actually a little emberassed, now, but yes: this is exactly why I was getting confused. Thanks. That doesn't answer the question, however; it just helps me to phrase it properly. `------------ :Wq Not an editor command: Wq` [download]	[reply] [d/l]