Subject FW: [IBO] How to set field value on update?
Author Alan McDonald
heLen, good reason to use NOW... I thought someone said a while ago that NOW
is being phased out in favour of SQL99 standard CURRENT_TIMESTAMP but there
is good currency to use NOW and keep it operational in FB??
Alan

> -----Original Message-----
> From: Helen Borrie [mailto:helebor@...]
> Sent: Sunday, 1 December 2002 14:41
> To: IBObjects@yahoogroups.com
> Subject: Re: [IBO] How to set field value on update?
>
>
> At 03:23 AM 01-12-02 +0000, you wrote:
> >--- In IBObjects@y..., Paul Vinkenoog <paulvink@s...> wrote:
> > >
> > > I think CURRENT_TIMESTAMP ought to work.
> > >
> >
> >Thanks a lot! I cannot find detail mention of these date functions in
> >the IB6 manual (downloaded from borland). I will be grateful if you
> >could give me pointer to better IB6 documentation, so that I don't
> >need to ask stupid questions in this list.
>
> Well, you would have found doc of date literals in the DataDef.pdf. You
> could have used CAST('NOW' AS TIMESTAMP). It gives you a more accurate
> timestamp, since CURRENT_TIMESTAMP stays constant throughout a
> transaction,
> whereas 'NOW' gives you the timestamp at the moment the update or insert
> occurs.
>
> A lot of the documentation changes for IB 6 can be found in the Migration
> Guide and in the IB 6.0 release notes.
>
> Firebird manuals are available from IB Phoenix, on their CD. An updated
> version is due out this week. Not free: but you get a feast of
> goodies on
> the CD.
>
> Helen
>
>
>
> __________________________________________________________________
> _________
> IB Objects - direct, complete, custom connectivity to Firebird or
> InterBase
> without the need for BDE, ODBC or any other layer.
> __________________________________________________________________
> _________
> http://www.ibobjects.com - your IBO community resource for Tech
> Info papers,
> keyword-searchable FAQ, community code contributions and more !
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>