Definitely getting it fixed!
This is one of the worst kind of bugs. You would never test for it. Furthermore when I first became aware of it I assumed it was some weird artefact of the upgrade and simply reloaded the existing procedure. Of course we then tested it straight after a reload and look the date/times are OK...it never occurred to me to wait ten seconds and have another try.
Kicking myself on that one!
Marty
-----Original Message-----
From: Martin Crouch [mailto:spamspamspam (AT) spaml (DOT) com]
Sent: 03 August 2012 10:39
To: info-ingres (AT) kettleriverconsulting (DOT) com
Subject: Re: [Info-Ingres] dates and procedures in 10.1
On 03/08/2012 09:30, Ingres Forums wrote:
Quote:
Just delete the second occurrence of *declare*; it shouldn't be there.
Sorry I didn't try my code before posting (don't have a Ingres 10.1 installation). But the basic idea was to use a variable sourced from the database (containing now) rather than a constant. This means that it shouldn't get optimised and has to be calculated at run time.
|
Even if the above works the original bug should be fixed...
_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://ext-cando.kettleriverconsulti...fo/info-ingres