Ludek Finstrle wrote:
> > > 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.
'?' doesn't necessarily mean a data_at_execution parameter.
Doesn't your patch change all parameters to data_at_exec ones ?
If so it doesn't seem good.
In response to
pgsql-odbc by date
|Next:||From: Larry Rosenman||Date: 2001-03-22 04:04:00|
|Subject: odbc/UnixWare 7.1.1: No Go.|
|Previous:||From: Bruce Momjian||Date: 2001-03-21 21:17:22|
|Subject: New Unapplied Patches web page|