Postgres Pro
Downloads
Home   >   mailing lists

Thread: ODBC, SQLExecute and HY010

ODBC, SQLExecute and HY010

From
"Brian J. Erickson"
Date:
Hello,

I have been getting intermentent errors
with SQLExecute.
Using SQLGetDiagRec, I get:
"HY010\nError Code: 3\nConnection is already in use."

I am running:
The latest postgresql ODBC driver.
Windows 2000
VC++ 6.0
The application is muliti-threaded.
Functions are called via CRecordset.

I have wrapped the queries in critical
sections, which seemed to minimized
the problem, but not eliminate it.

The problem seems to be occuring in the function:
SC_execute(StatementClass *self)
Line:  conn->status = CONN_EXECUTING;
Lines: if (CONN_DOWN != conn->status)
        conn->status = oldstatus;

If I set the next execution line for the SQLExecute function,
the command executes just fine.

I have tried to generate a log file, but it doesn't seem
to helpful.

Thanks.

----------------------------Log File-----------------------------------
[1036]CopyCommonAttributes:
A7=100;A8=4096;A9=0;B0=254;B1=8190;B2=0;B3=0;B4=1;B5=1;B6=0;B7=1;B8=0;B9=1;C
0=0;C1=0;C2=dd_;[1036]attribute = 'UID', value = 'account'
[1036]CopyCommonAttributes:
A7=100;A8=4096;A9=0;B0=254;B1=8190;B2=0;B3=0;B4=1;B5=1;B6=0;B7=1;B8=0;B9=1;C
0=0;C1=0;C2=dd_;[1036]attribute = 'Servername', value = 'host'
[1036]CopyCommonAttributes:
A7=100;A8=4096;A9=0;B0=254;B1=8190;B2=0;B3=0;B4=1;B5=1;B6=0;B7=1;B8=0;B9=1;C
0=0;C1=0;C2=dd_;[1036]attribute = 'Password', value = 'xxxxx'
[1036]CopyCommonAttributes:
A7=100;A8=4096;A9=0;B0=254;B1=8190;B2=0;B3=0;B4=1;B5=1;B6=0;B7=1;B8=0;B9=1;C
0=0;C1=0;C2=dd_;[1036]attribute = 'Database', value = 'database'
[1036]CopyCommonAttributes:
A7=100;A8=4096;A9=0;B0=254;B1=8190;B2=0;B3=0;B4=1;B5=1;B6=0;B7=1;B8=0;B9=1;C
0=0;C1=0;C2=dd_;

Re: ODBC, SQLExecute and HY010

From
Hiroshi Inoue
Date:
"Brian J. Erickson" wrote:
>
> Hello,
>
> I have been getting intermentent errors
> with SQLExecute.
> Using SQLGetDiagRec, I get:
> "HY010\nError Code: 3\nConnection is already in use."
>
> I am running:
> The latest postgresql ODBC driver.
> Windows 2000
> VC++ 6.0
> The application is muliti-threaded.
> Functions are called via CRecordset.
>
> I have wrapped the queries in critical
> sections, which seemed to minimized
> the problem, but not eliminate it.
>
> The problem seems to be occuring in the function:
> SC_execute(StatementClass *self)
> Line:  conn->status = CONN_EXECUTING;
> Lines: if (CONN_DOWN != conn->status)
>         conn->status = oldstatus;
>
> If I set the next execution line for the SQLExecute function,
> the command executes just fine.

Could you trythe latest snapshot at
    http://www.geocities.jp/inocchichichi/psqlodbc/ ?

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

Re: ODBC, SQLExecute and HY010

From
"Brian J. Erickson"
Date:
Hello,

That seemed to solve the problem.

Thanks

Brian Erickson

----- Original Message -----
From: "Hiroshi Inoue" <Inoue@tpf.co.jp>
To: "Brian J. Erickson" <ericksbr@infocon-inc.com>
Cc: <pgsql-odbc@postgresql.org>
Sent: Monday, September 01, 2003 8:21 PM
Subject: Re: [ODBC] ODBC, SQLExecute and HY010


> "Brian J. Erickson" wrote:
> >
> > Hello,
> >
> > I have been getting intermentent errors
> > with SQLExecute.
> > Using SQLGetDiagRec, I get:
> > "HY010\nError Code: 3\nConnection is already in use."
> >
> > I am running:
> > The latest postgresql ODBC driver.
> > Windows 2000
> > VC++ 6.0
> > The application is muliti-threaded.
> > Functions are called via CRecordset.
> >
> > I have wrapped the queries in critical
> > sections, which seemed to minimized
> > the problem, but not eliminate it.
> >
> > The problem seems to be occuring in the function:
> > SC_execute(StatementClass *self)
> > Line:  conn->status = CONN_EXECUTING;
> > Lines: if (CONN_DOWN != conn->status)
> >         conn->status = oldstatus;
> >
> > If I set the next execution line for the SQLExecute function,
> > the command executes just fine.
>
> Could you trythe latest snapshot at
> http://www.geocities.jp/inocchichichi/psqlodbc/ ?
>
> regards,
> Hiroshi Inoue
> http://www.geocities.jp/inocchichichi/psqlodbc/
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
>       joining column's datatypes do not match
>