Re: Date precision problem

> I having some problem with the date fields migration from 7.1.3 version to 7.2
> version...
> In the new version PostgreSQL 7.2 on i686-pc-linux-gnu, compiled by GCC 2.96
> The date is different in the last part:
> 2002-04-11 13:02:27.943119+02
> ^^^^^^^^^
> Then when I am trying to update this field from ACCESS I have an error and the
> entry can't be updated because the dates are not equals.

Could you be more specific about the problem? I first interpreted this
as a problem with now(), but now that I read this again you are talking
about updating fields so that is not the actual test case is it?

What entry are you updating? What are you comparing to be equal? Is this
some funny business with Access generating updates from keys it is
holding internally (I recall something about it doing that)?

If for some reason you need less precision in your date/times, you can
now explicitly set the precision of a column:

thomas=# select timestamp without time zone 'now',
thomas=> timestamp(2) without time zone 'now',
thomas=> timestamp(0) without time zone 'now';
timestamp | timestamp |
timestamp
----------------------------+------------------------+---------------------
2002-04-17 06:34:33.032644 | 2002-04-17 06:34:33.03 | 2002-04-17
06:34:33

But afaik others have not seen a problem; could you have some funny
settings in Access which are causing your queries to fail? I haven't
used it myself, so can't help in more detail I'm afraid...

- Thomas