Re: Q: SPL, CURRENT, BEGIN, COMMIT ?

In article <9611201632.aa15060@qwsserv.qws.msk.su>, Victor says... > >Hi all, > >We are running INFORMIX (Online 7.10.UC1) on SCO UNIX 3.2v5.0.0. >Database created with log. > > >Test N 1 : >---------- >CREATE PROCEDURE xxx()> DEFINE current_date_time DATETIME YEAR TO FRACTION(2); > >{ 1 } LET current_date_time = CURRENT; > >END PROCEDURE; >EXECUTE PROCEDURE xxx();>dbaccess: Procedure executed. > > >Test N 2 : >---------- >CREATE PROCEDURE xxx()> DEFINE current_date_time DATETIME YEAR TO FRACTION(2); > >{ 1 } BEGIN WORK; >{ 2 } LET current_date_time = CURRENT; >{ 3 } COMMIT WORK; > >END PROCEDURE; >EXECUTE PROCEDURE xxx();>dbaccess: Procedure executed. > > >Test N 3 !!! : >-------------- >DROP PROCEDURE xxx; >CREATE PROCEDURE xxx()> DEFINE current_date_time DATETIME YEAR TO FRACTION(2); > >{ 1 } BEGIN WORK; >{ 2 } COMMIT WORK; > >{ 3 } LET current_date_time = CURRENT; > >END PROCEDURE; >EXECUTE PROCEDURE xxx();>dbaccess: 1263: A field in a datetime or interval value is out of range > or incorrect. > >Does anybody can explain me such behaviour ? >Many thanks in advance. Hello, I've seen this (or something close) in 7.10 on HP. In one particular case it was connected with audit - as soon as you turn it off the damn thing starts to work... It looks like nearly all CURRENT in SPL "peculiarities" are reported as resolved in 7.11(cannot tell for sure about this particular case) but 7.11 itself is not worth to upgrade to - very buggy! If you wish to upgrade I'd recommend 7.14 or further 7.20/21 Regards, Ilya Bogorad DHL Systems LTD/ London - UK