Getting precise values for TIMESTAMP(n) columns

I think you want to use CURRENT_TIMESTAMP or LOCAL_TIMESTAMP they should
both include milliseconds, for more info see:

http://newsgroups.derkeiler.com/Archive/Comp/comp.databases.ingres/2008-
04/msg00017.html

This works for me.

Regards

Anthony Simpson
Luminary - An Ingres Company
Tel: +44 (0) 845 371 4090
Mob: +44 (0) 7833596587
Email: anthony.simpson.DeleteThis@luminary.co.uk

For more information on Luminary go to http://www.luminary.co.uk
Luminary Solutions Limited Registered in England No 4854134 VAT Reg No.
829 3166 13
Registered Office: Lacon House, Theobald's Road, London, WC1X 8RW

-----Original Message-----
From: info-ingres-bounces.DeleteThis@kettleriverconsulting.com
[mailto:info-ingres-bounces@kettleriverconsulting.com] On Behalf Of Roy
Hann
Sent: 14 October 2008 11:26
To: info-ingres.DeleteThis@kettleriverconsulting.com
Subject: Re: [Info-Ingres] Getting precise values for TIMESTAMP(n)
columns

Roy Hann wrote:

> I have been trying to find a way to get Ingres to supply a timestamp
> with millisecond precision (and accuracy) to store in a TIMESTAMP(3)
> column in a database procedure. So far I've come up empty-handed.
> Anyone got any suggestions?

One of my colleagues who hadn't even seen this just phoned me out of the
blue to tell me that a TIMESTAMP column WITH DEFAULT will be given the
current time when you insert a row. That's a good start, although I
will have to hold my nose if I am going to rely on a default value when
inserting.

Now, what can I do about timestamps for updates?

--
Roy

UK Ingres User Association Conference 2009 will be on Tuesday June 9,
2009
Go to http://www.iua.org.uk/join to get on the mailing list.


_______________________________________________
Info-Ingres mailing list
Info-Ingres.DeleteThis@kettleriverconsulting.com
http://www.kettleriverconsulting.com/mailman/listinfo/info-ingres
 >> Stay informed about: Getting precise values for TIMESTAMP(n) columns 

Anthony Simpson wrote:

> I think you want to use CURRENT_TIMESTAMP or LOCAL_TIMESTAMP they should
> both include milliseconds, for more info see:
>
> http://newsgroups.derkeiler.com/Archive/Comp/comp.databases.ingres/2008-
> 04/msg00017.html

That's just what I needed. Thanks.

--
Roy

UK Ingres User Association Conference 2009 will be on Tuesday June 9, 2009
Go to http://www.iua.org.uk/join to get on the mailing list.
 >> Stay informed about: Getting precise values for TIMESTAMP(n) columns