Re: OTL database access class

From: Mike Krolewski <mkrolewski_at_rii.com>
Date: Wed, 27 Dec 2000 18:51:58 GMT
Message-ID: <92ddob$mde$1_at_nnrp1.deja.com>


[Quoted] In article <LLo26.27256$RC1.933699_at_newsread1.prod.itd.earthlink.net>,   "Doug Farrell" <dfarrell01_at_earthlink.net> wrote:
> Hi,
> I'm new to Oracle but have written some PL/SQL that is part of a C++
 class.
> To say the least I find this to be a poor solution to getting data
 from our
> Oracle database. Does anyone have any experience with OTL database
 library?
> URL : http://www.geocities.com/skuchin/otl/home.htm
>
> I've looked at it and it looks pretty good, but I was wondering if
 anyone
> who has used it would care to comment on their experiences.
>
> Thanks in advance,
> Doug
>
>

[Quoted] I used it for about 2 years. The OTL is a major improvement over OCI. OCI has too many cryptic parameters.

I do not think you will find it any easier than PL/SQL. You have the same problems with binding and collecting data from any statement. IMHO proC is more obvious. I like using the method 4 as it gives me the most control over activities. You still need to construct the binding structures, and indicator variables. I have built up a template for doing any fetch -- replacing the cursor name (need new one for each cursor ), filling in the actual query, and updating the cursor structure, and of course the fetch area. I generally build this like a file operation with an open, fetch and close procedure. Within the fetch, I typically translate the data into a more reasonable C/C++ object or structure.

After the procedures are written, I can focus on the real reason for writing the C++ program. Again, I would like to think that one should use PL/SQL if all you are doing is within the database. The PL/SQL is more reliable and rapid then translating into another language.

--
Michael Krolewski
Rosetta Inpharmatics
mkrolewski_at_rii.com
              Usual disclaimers


Sent via Deja.com
http://www.deja.com/
Received on Wed Dec 27 2000 - 19:51:58 CET

Original text of this message