[Info-ingres] Weird problem in Ingres 10

[Laframboise, André (BAC/LAC)]

When you say no errors, does that mean the SQL statement returns a successful return code ?
Or is the code only trapping certain non-successful RCs ?

André Laframboise

Conseiller Principal Base de Données, Direction générale de l'Innovation et du Dirigeant principal de l'information
Bibliothèque et Archives Canada / Gouvernement du Canada
andre.laframboise at canada.ca / Tél. : 613-298-1346

Senior Database Advisor, Innovation and Chief Information Officer Branch
Library and Archives Canada / Government of Canada
andre.laframboise at canada.ca / Tel: 613-298-1346

-----Original Message-----
From: info-ingres-bounces at lists.planetingres.org <info-ingres-bounces at lists.planetingres.org> On Behalf Of Mark
Sent: Wednesday, May 16, 2018 7:44 AM
To: info-ingres at lists.planetingres.org
Subject: Re: [Info-ingres] Weird problem in Ingres 10

On Tue, 15 May 2018 12:27:09 -0400, Karl and Betty Schendel <schendel at kbcomputer.com> wrote:

>It's certainly not something I have heard of or seen before.  Do you 
>have any rules defined on the relevant tables?  Try enabling LOG_TRACE 
>if the problem is sufficiently predictable, or do a logdump after the 
>problem occurs if it's not; the idea being to try to see whether you 
>actually got any PUT (insert) or REP (replace) log records that were 
>then rolled back, or whether the insert / update was never executed at all.

After enabling log_trace all I got was:

    LOG: SAVEPOINT   Size written/reserved:      0/     0  Flags:
-------------------------------------------------------------------


>Karl
>
>> On May 15, 2018, at 11:41 AM, Mark <i at dontgetlotsofspamanymore.net> wrote:
>> 
>> We have C code using embedded SQL to access Ingres databases.  The 
>> relevant code has been working for a long time.  Recently we have 
>> experienced occasions where the first time an INSERT or UPDATE 
>> statement is executed the data is not inserted or updated, but no 
>> errors are reported.  Subsequent cases where the same code is excuted 
>> work fine.  This problem has only occurred on Ingres 10 databases on 
>> Linux and the same code with Ingres 9 works fine.
>> 
>> I know this is very little to go on but does anyone have any idea 
>> what could be wrong???
>> 
>> --
>> <insert witty sig here>
>> _______________________________________________
>> Info-ingres mailing list
>> Info-ingres at lists.planetingres.org
>> http://lists.planetingres.org/mailman/listinfo/info-ingres

--
<insert witty sig here>
_______________________________________________
Info-ingres mailing list
Info-ingres at lists.planetingres.org
http://lists.planetingres.org/mailman/listinfo/info-ingres