Re: IDS 7.3 : Stored procedures tuning

From: Arnaud ANDRIEUX <arnaud.andrieux@aql.fr> > >Thanks but I still have some troubles : > > > select current from systables where tabid = 1; > > execute procedure fred("right"); > > select current from systables where tabid = 1;> >The CURRENT function always returns result wich precision is 'truncated' to >second format (fraction part of datetime is always 000) : '2000-04-04 >15:21:54 000'. I get this result either in an SQL statement or in a SP. I >read that CURRENT rely on the system date and time API ; I suppose that >WinNT >knows millisecond ! So I do not really understand what is the problem ! In your onconfig file, set USEOSTIME to 1. > > Or some variation on that theme. > > > > Or: > > > > SELECT dbinfo('utc_current') in your SP. > >Wich format returns this statement (I did not find 'utc_current' in >documentation, what is it ?) because I get an exception of bad conversion >when I set this statement in a DATETIME YEAR TO FRACTION variable ? Why don't you select it into a char? Then you can work out how it comes back. ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com

Obnoxio The Clown wrote: > >The CURRENT function always returns result wich precision is 'truncated' to > >second format (fraction part of datetime is always 000) : '2000-04-04 > >15:21:54 000'. I get this result either in an SQL statement or in a SP. I > >read that CURRENT rely on the system date and time API ; I suppose that > >WinNT > >knows millisecond ! So I do not really understand what is the problem ! > > In your onconfig file, set USEOSTIME to 1. Doesn't works!