From: | Ludek Finstrle <xfinstrl(at)informatics(dot)muni(dot)cz> |
---|---|
To: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
Cc: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: pgsqODBC binding parameters II (fwd) |
Date: | 2001-03-21 10:38:34 |
Message-ID: | 20010321113834.D21919@anxur.fi.muni.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> > please, could some expert answer?
>
> Though I'm not an expert, I have a question.
>
> [snip]
>
> > > CONN ERROR: func=SQLExecute, desc='', errnum=110, errmsg='ERROR: parser: parse error at or near ""'
> > > SQLExecute: premature statement so return SQL_ERROR
>
> PREMATURE state of the statement seems to be the cause of
> the error. Is your change about data_at_exec to prevent the
> PREMATURE state just after the return from SQLNumResultCols ?
> Or does it have another purpose ?
Sorry, I don't understand question very well.
I make it in december. So I don't remember details.
The problem was that '?' didn't be detect as parametr at exec.
So I added detection of parameters at exec to SQLExecute. And if I detect
it I return SQL_NEED_DATA.
Do you want logs with successfull execute?
Luf
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2001-03-21 11:27:21 | RE: MULTIBYTE support |
Previous Message | Hiroshi Inoue | 2001-03-21 09:44:46 | Re: MULTIBYTE support |