Alternatives to writing an ODBC driver

views:

answers:

+3 Q:

Alternatives to writing an ODBC driver

We are storing allot of time series data into our own proprietary "database". In the next version of our system we want to give our users a simple query mechanism to extract the raw data from the database (as a complement to the reports our system can create) by using standard tools.

I have looked at the possibility to write an ODBC driver, but it looks like quite a daunting task, especially when the use will be very simple select statements.

I would be grateful for any tips, ideas and/or recommendation of libraries, that could make this task a bit simpler.

Our platform is Windows and our dev. env. is visual studio 2010 (nativ C++)

It depends on what makes your customers happy. Easier than an writing ODBC driver would seem to provide a library function that can parse simple SQL selects and deliver the result in whatever form desired.

Peter G. 2010-10-30 15:52:33

Yes, agree. But it looks like he wants ODBC to allow his customers to use standard tools: I.E. Crystal Reports to generate Reports against his proprietary database.

Pablo Santa Cruz 2010-10-30 15:53:47

+2 A:

A LINQ provider.

Remus Rusanu 2010-10-30 15:54:45

have to look into that, the interface to the "database" is a RPC interface, never used that in C# before, I guess you implement the whole thing as a dll or com object that talks via RPC to the "database"

RA 2010-10-30 16:02:55

+1 Can it get any easier?

Peter G. 2010-10-30 16:05:37

@RA: You would need a protocol to talk between your manager LINQ provider and your back end. I would use REST and this would also give me REST access to the back end. But I have to say, none of these brings the majority of commercial products *any* closer, since the vast majority require ODBC or OleDB access.

Remus Rusanu 2010-10-30 16:15:53

@remus thanks for the input , will take a closer look at it, but as you say, this maybe more for advanced customers integrating data in their own systems, than the people we have in mind, that is equipped with Toad and a bit of SQL knowledge.

RA 2010-10-30 18:18:15

It might be interesting to take a look at OData, exposing your data as an OData producer, you would then be able to allow your users to query it right away using the already available consumers, e.g. Linqpad.

steinar 2010-10-30 15:59:56

Looks interesting but the SDK, only problem seems to be a .Net/java only SDK.

RA 2010-10-31 16:26:32

ansaurus

tags:

views:

answers:

Alternatives to writing an ODBC driver

related questions