From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From: =?UTF-8?B?QmrDtnJuIEx1bmRpbg==?= <b.f.lundin@gmail.com>
Newsgroups: comp.lang.ada
Subject: Re: Compiling GNATColl on Windows
Date: Tue, 16 Dec 2014 00:14:07 +0100
Organization: A noiseless patient Spider
Message-ID: <m6nps6$jmt$1@dont-email.me>
References: <09729271-32e5-4d7e-999f-2299a9c975fd@googlegroups.com>
 <27f6331d-31d4-4626-9b41-327c49bcbb6e@googlegroups.com>
 <5988fe56-ed84-4a6b-b5dd-d453b3c3b2f6@googlegroups.com>
 <8e88a5bd-30ab-4a23-974f-6fbeff11fb8c@googlegroups.com>
 <9a7fe568-2d34-42be-b1be-ce0653af005b@googlegroups.com>
 <m6nl8c$25m$1@dont-email.me> <1ifoukt5d2s2z$.6d9y7y2fiufo$.dlg@40tude.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 15 Dec 2014 23:12:06 +0000 (UTC)
Injection-Info: mx02.eternal-september.org;
 posting-host="9aeff6368c164dc50b2215b3caf5ef4a";
	logging-data="20189"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX196zeoEhJyL/cG5uz8Mo3Ne"
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Icedove/31.2.0
In-Reply-To: <1ifoukt5d2s2z$.6d9y7y2fiufo$.dlg@40tude.net>
Cancel-Lock: sha1:TtRCQxa4g30DKwPfxfgCrV/3QYI=
Xref: news.eternal-september.org comp.lang.ada:24027
Date: 2014-12-16T00:14:07+01:00
List-Id: <comp.lang.ada>

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