> > > *However*, whilst testing I did find an issue with SQLTables that
> > > seems surprisingly similar to the one you fixed before. It's pretty
> > > easy to recreate in the Microsoft test suite.
> >
> > I didn't fix something similar. I don't remember it at least. Could
> > you be more specific? I only point at Prepare, Execute, Execute or
> > ExecDirect, ExecDirect problem.
>
> There was a fix for SQLTables where Declare/Fetch messed things up for
> Borland SQL Explorer/BDE by duplicating rows.

Yes. I didn't think it's problem. But maybe it is.

> > > - Connect to a data source with Declare/Fetch enabled.
> > > - SQLExecDirect "SELECT * FROM pg_class"
> > > - Get Data All (from the results menu)
> > > - SQLTables
> > > - Get Data All
> > >
> > > It never stops retrieving data! Seems that you need to do the
> > > SQLExecDirect first - SQLExecute doesn't trigger the problem.
> > > SQLColumns is similarly affected - perhaps there are more as well.
> >
> > I'm unable reproduce it here. I have CVS source with
> > autocommit_off patch.
> > It stops when I expect.
>
> Odd.

You forgot say that you setup cache size to 10 :-) That's the difference.
I read it from log. So I'm able to reproduce the problem now.

Regards,

Luf

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

> > > I didn't fix something similar. I don't remember it at least. Could
> > > you be more specific? I only point at Prepare, Execute, Execute or
> > > ExecDirect, ExecDirect problem.
> >
> > There was a fix for SQLTables where Declare/Fetch messed things up for
> > Borland SQL Explorer/BDE by duplicating rows.
>
> Yes. I didn't think it's problem. But maybe it is.

I rollbacked the patch and problem is still here. I locate it
and fix. Patch attached.

There is problem in mixing different STMTs :-(

Luf


---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org