Thread: Need Help w/ Timestamps

Hi!

I moved all of our PostGRE DBs from Windows to Linux last weekend.
Everything went well, performance is great, BUT there is one issue that I
need to solve.

My problem is, that the precision for timestamps in Linux is greater than in
Windows. That seems to be fine, but MS Access cannot handle it. E.g.:

   Windows Timestamp: 2006-09-08 15:25:42.332
   Linux Timestamp:   2006-09-09 21:25:06.947069

Is there any way (even somehow through the ODBC driver) to restrict the
timestamp accuracy to "M$ Win" accuracy?

Thanks for your help!

-Enrico

On Mon, 11 Sep 2006 10:05:14 -0500
Enrico Riedel <eriedel@thunderelectricinc.com> wrote:

> My problem is, that the precision for timestamps in Linux is
> greater than in Windows. That seems to be fine, but MS Access
> cannot handle it. E.g.:
>
>    Windows Timestamp: 2006-09-08 15:25:42.332
>    Linux Timestamp:   2006-09-09 21:25:06.947069
>
> Is there any way (even somehow through the ODBC driver) to restrict
> the timestamp accuracy to "M$ Win" accuracy?

http://www.postgresql.org/docs/7.4/static/functions-datetime.html#FUNCTIONS-DATETIME-TRUNC

???


--
Ivan Sergio Borgonovo
http://www.webthatworks.it

On Mon, 2006-09-11 at 10:05, Enrico Riedel wrote:
> Hi!
>
> I moved all of our PostGRE DBs from Windows to Linux last weekend.
> Everything went well, performance is great, BUT there is one issue that I
> need to solve.
>
> My problem is, that the precision for timestamps in Linux is greater than in
> Windows. That seems to be fine, but MS Access cannot handle it. E.g.:
>
>    Windows Timestamp: 2006-09-08 15:25:42.332
>    Linux Timestamp:   2006-09-09 21:25:06.947069
>
> Is there any way (even somehow through the ODBC driver) to restrict the
> timestamp accuracy to "M$ Win" accuracy?
>

select now()::timestamp(3);