Hey,
Marcin Kasperski wrote:
>>>>Absolutely. I'm already interested in an Oracle back-end (or
>>>>rather, if I had one now, I could "sell" Subverison to a
>>>>very, very, rich company...)
>>>>
>>>>
>>>FYI as an OCI hacker I wouldn't mind helping out on this.
>>>I'm probably one of the few brave souls who's actually
>>>written code directly to OCI not the Pro*C/C++ preprocessor.
>>>
>>>
>>There you go! OCI is the only way to go in my opinion.
>>
>>
>
>In my too. Of course the first thing to do while programming with
>OCI is to write some normally looking library over it or choose
>one existing.
>
>AFAIK there are at least two open-source libraries covering OCI
>with more natural API (Ora++ and OTL). In my organization we
>have written our own library so I can't comment on them but this
>could be a way to go.
>
>
Yup! I started one. It was working in cheesy test cases on linux
sitting over ODBC->Mysql. I also started a native Mysql and I think a
OCI adapter (s) for it. The main reason I started writing my own was
that at the time I didn't find anything for C. Plus, my stuff uses APR
for everything it could. It does do some things differently than
traditional JDBC ODBC. For instance, it supports loading SQL statements
from Subversion config files. It supports identification of parameters
and parameter types in those files as well. Actually, quite a bit more
now that I think of it. Of course, that code hasn't been run in about
18 months:-) But I can get it going when the plugin stuff is in place.
>Pro*C/C++ is terrible. Avoid it.
>
I don't know if I'd call it terrible. It's just tooooo proprietary.
gat
Received on Fri Apr 2 23:12:32 2004