Re: Compiling GNATColl on Windows

["Björn Lundin" <b.f.lundin@gmail.com>]

On 2014-12-15 23:37, Dmitry A. Kazakov wrote:
> No need to fiddle with cursors explicitly and nothing to commit, if only
> reading.

hmm, yes. I got the spec from work, where we use Oracle
and Ms-sql-server from win and Aix.
I wanted the pg-interface to be code compatible,
with that, for future use. - If we ever start using pg at work.
The idea is that any interaction with the db, with no transaction,
is a sign of error. Thats why a transaction is needed.
Good or bad, that is the reason, libpq itself need no transaction for
read-only.

> ODBC has a lot of problems, but it usually is simpler than native clients.

I've had problems using a cursor in a cursor with ODBC.

  T.Start;
  Stm.Set("A",Some_Value);
  Stm.Open_Cursor;
  Stm.Fetch(End_Of_Set);
  If not End_of_set then
    Stm.Get("COL1",Some_Variable);
    Stm2.Set("COL3", Some_Variable) -- use value from stm in stm2
    Stm2.Execute;      <-- bang - crash
  end if;
  Stm.Close_Cursor;
  T.Commit;

Turned out I had to enable mars - multiple active recordset
But did not work on unix-odbc from linux with sql-server.

And I do not even dare to try it on AIX.
Native client however, works fine.

But for windows, perhaps odbc is a better choise

--
Björn