Exactly, with using 'timestamp' you gain data integrity as the database
will make sure that it only accepts valid timestamps. So, if your code
that you use to INSERT gets skewed someway, it will fail if you try to
insert an invalid number.
-Robby
On Fri, 2004-07-30 at 14:26, Glen Parker wrote:
> However it may be represented, it IS a timestamp, so why not use a timestamp
> data type if you have one available to you? That's what data types are for
> after all...
>
> > So, I'm recording the timestamp from some unix files.
> >
> > Any opinions as to whether it's best to use a "bigint"
> > (which matches the file system data) or a "timestamp"
> > (which might be easier to manipulate in the database)?
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
--
Robby Russell | Owner.Developer.Geek
PLANET ARGON | www.planetargon.com
Portland, OR | robby@planetargon.com
503.351.4730 | blog.planetargon.com