Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Gary L. Burnore — — source: Informix-list mailing list archive (1991-1998)
On Mon, 17 Aug 1998 15:09:08 -0400, in article
<35D87FD4.D7C@exchange.sms.siemens.com>, Rich Sy
<Richmont.Sy@exchange.sms.siemens.com> wrote:
>We have informix online 5.0 and esqlc 4.10.U. We want to use perl
>5.00404 to interface with informix. So far we've not found any
>available perl interface to informix that can make use of what we
>currently have. I thought I've found something with the older 'isqlperl'
>but it only compiles with perl 4.
>
>Can anyone suggest any strategy as to how we can quickly and efficiently
>interface with informix? We don't have the expertise nor the time to
>extend perl.
>
>We were thinking along the line of spawning an esqlc program from perl
>that has all the informix connections available and communicate with the
>perl parent process via some sort of an ipc. We thought we could use
>dynamic sql but found that statements such as "describe...from" and
>"allocate descriptor" do not compile in our current version of esqlc.
Your version of esqlc is not new enough for dsql. Try upgrading.
--
I DO NOT WISH TO RECEIVE EMAIL IN REGARD TO USENET POSTS
---------------------------------------------------------------------------
How you look depends on where you go.
---------------------------------------------------------------------------
Gary L. Burnore | '۳'''''''ۺ''''''''''۳
| '۳'''''''ۺ''''''''''۳
DOH! | '۳'''''''ۺ''''''''''۳
| '۳ 3 4 1 4 2 '' 6 9 0 6 9 '۳
Special Sig for perl groups. | Official Proof of Purchase
===========================================================================
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.