Home » U++ Library support » U++ SQL » Timestamp accuracy in postgres and upp
Re: Timestamp accuracy in postgres and upp [message #33090 is a reply to message #33055] |
Wed, 06 July 2011 14:30 |
|
mirek
Messages: 13980 Registered: November 2005
|
Ultimate Member |
|
|
Zbych wrote on Tue, 05 July 2011 09:44 | Hi,
Definition of TIME in database schematic doesn't specify accuracy and (at least) postgres keeps time in micro seconds. Since upp time accuracy is 1s, it sometimes leads to some problems. Maybe there should be another definition of TIME that has the same accuracy like upp? What do you think?
My proposition is to add following definitions to PostgreSQLSchema.h:
#define TIME_SEC(x) COLUMN("timestamp(0)", Time, x, 0, 0)
#define TIME_SEC_(x) COLUMN_("timestamp(0)", Time, x, 0, 0)
|
Actually, perhaps TIME should be defined in seconds accuracy...
However, what kind of issues does it leads to? I would say you store seconds, you are about retrieve seconds from DB, right?
Mirek
|
|
|
Goto Forum:
Current Time: Thu May 16 14:57:06 CEST 2024
Total time taken to generate the page: 0.01731 seconds
|