Re: Client software vs cursor problem? - Mailing list pgsql-odbc

From Hiroshi Inoue
Subject Re: Client software vs cursor problem?
Date
Msg-id 3EFA6BEE.1E3ED48F@tpf.co.jp
Whole thread Raw
In response to Client software vs cursor problem?  (Richard Huxton <dev@archonet.com>)
Responses Re: Client software vs cursor problem?  (Richard Huxton <dev@archonet.com>)
List pgsql-odbc
Which version of psqlodbc driver are you using ?

regards,
Hiroshi Inoue
    http://www.geocities.jp/inocchichichi/psqlodbc/

Richard Huxton wrote:
>
> I've got a client trying to access PG through ODBC from something called ENVOX
> (a telecomms IVR system). It lets you build control scripts visually by
> dragging/dropping boxes and setting some params.
>
> Now, if he uses a SELECT box to open a (static) cursor then an INSERT box to
> add a record it fails, but *only* if the select returns no records. If the
> INSERT box is replaced by a "RAWSQL" box he can successfully build his own
> insert statement and run it. He's happy enough with this workaround, but it'd
> be good if we can figure out what's happening.
>
> The error he gets is "row value out of range" which appears to be HY107 from
> googling. This suggests to me the INSERT box is trying to move to the
> first/last row or similar and failing because there are no rows.
> Unfortunately I'm no ODBC expert and can't see what code underlies the box.
>
> Two questions:
> 1. Does it sound like I'm on the right track?
> 2. Would getting him to turn on odbc-logging at his end help me to diagnose?
> (he's remote from me).
>
> Oh - we've tried variations on the cursor type and cursor-concurrency settings
> and they seem to make no difference.

pgsql-odbc by date:

Previous
From: Richard Huxton
Date:
Subject: Client software vs cursor problem?
Next
From: Richard Huxton
Date:
Subject: Re: Client software vs cursor problem?