Mark Rotteveel wrote: >> - When used as shorthand casts / datetime literals they are evaluated only >> once: at parse/prepare time. In this case, they are often*less* up-to-date >> than the CURRENT_<DATETIME> variables, because the latter are refreshed >> every time a prepared query is executed again. > To me this difference sounds like a bug, not a 'feature'.
There is a specific requirement for both styles of literal. If you are adding a lot of data which needs to be identified as in the same batch, then you want the SAME timestamp on every record in a commit, you use the 'CURRENT_x' literals. If you want to timestamp each element as it is processed, then you use the original 'NOW' timestamp. The legacy shortcuts to yesterday,today and tomorrow are probably questionable, but need to be retained for BC reasons. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk// Firebird - http://www.firebirdsql.org/index.php ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
