Re: Q: SPL, CURRENT, BEGIN, COMMIT ?
On 20 Nov 1996 16:32:26 +0300, Victor Kronberg <kron@qws.msk.su>
wrote:
>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.
>
>Best Regards, QWERTYS Ltd.
>Victor Kronberg, 10, Elektrodnaya St.,
>+7 (095) 368-8061 App # 425,
>E-Mail : kis@qws.msk.su Moscow, Russia,
>November 20, 1996, 16:30 111524.
>
Hi Victor,
We have the same problem with the function CURRENT.
To solve it we have changed texts of all stored procedures. We make
assignment value CURRENT to global variable before first transaction
and then use only this variable insted CURRENT. Also all clauses
'DEFAULT CURRENT' in column definition were removed.
Regards
Oleg Tretyakov
tov@inist.ru