[EMAIL PROTECTED] wrote:
On Mar 23, 3:49 pm, [EMAIL PROTECTED] (Dean Arnold) wrote:
Anyone know where the spec might be hiding ?
Last clue I had was some MSDN CD circa 2000.
Hi, Dean --
The ODBC info is still on the Microsoft site, albeit at a new URL.
Try here for the ODBC Programmer's Reference --
http://msdn2.microsoft.com/en-us/library/ms714177.aspx
The left-hand navigation drill-downs will take you to lots of other
data access information, among other things.
Yes, I'm aware of that, but I could swear there used to be a more
formal spec/SDK...but I'm progressing w/ those docs and a nice
DDJ article from some years ago.
I'm curious to know why you would need to build an ODBC driver for DBI
data sources -- and what would consume the results!
The notion has been kicked around here a few times in the past.
The primary motivation is to expose "exotic" DBD's (DBD::iPod,
DBD::Amazon, DBD::Google, DBD::Gofer, etc.) or subclasses (eg, DBIx::Chart)
some of us have written to a larger audience (eg, the mass of Excel
jockeys). Which might have the pleasant side effect of
- exposing more folks to Perl solutions
- motivating more people to write more exotic DBDs (eg, take a random
walk around programmableweb.com and pick some services to map
to DBDs)
- encouraging DBD authors to do a better job of conformance (yes, I'm guilty)
(in some sense, the resulting ODBC wrapper can act as a conformance
tester...*if* I can find a freely available conformance test suite
for ODBC)
There may be an existing solution for you, which may save a world of
> headache, as this is not the easiest of specifications to implement.
Hehe. I recall a flight home from a SQLAccess meeting in SillyCon Valley
many years ago, reading the 1st draft SQL CLI spec MSFT had dropped
in our collective laps, and thinking to myself, "No one in their right mind
will code to this interface...".
Which shows how feeble my prescient skills are.
However, using the aforementioned DDJ template helps leapfrog much
of the required ODBC internal yak-shaving. Ultimately, my hope is to provide
a liberally licensed FOSS solution.
- Dean
