On 6/2/03 11:04, "Ludwig Lim" <[EMAIL PROTECTED]> wrote:
> Are there cases when a TIME data type is a better
> choice over the TIMESTAMP data type?
Surely this depends on the nature of the data that you want to represent?
If you're researching into sleep patterns and want to represent the time
Hi Tomasz:
--- Tomasz Myrta <[EMAIL PROTECTED]> wrote:
>
> Probably you are right, but you can cast into
> timestamp before using these functions.
> Do you really need to care amount of storage?
I was just thinking if both TIMESTAMP and TIME have
use the same amount of space (I was think TIME
Ludwig Lim wrote:
Hi:
Are there cases when a TIME data type is a better
choice over the TIMESTAMP data type?
It seems that PostgreSQL (I'm using 7.2.3)
encourage its users to use TIMESTAMP over TIME data
type. I said this because of the following:
a) More functions for DATE and TIMES
Hi:
Are there cases when a TIME data type is a better
choice over the TIMESTAMP data type?
It seems that PostgreSQL (I'm using 7.2.3)
encourage its users to use TIMESTAMP over TIME data
type. I said this because of the following:
a) More functions for DATE and TIMESTAMP data types
su
