| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "'valeriof *EXTERN*'" <valerio_farruggio(at)hotmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Converting a TimestampTz into a C# DateTime |
| Date: | 2016-11-15 13:19:29 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B5397E777@ntex2010i.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
valeriof wrote:
> BTW, a comment says this about the floating point representation: "A
> deprecated compile-time option of PostgreSQL switches to a floating-point
> representation of some date/time
> fields. Npgsql (currently) does not support this mode." Is it safe to say
> that the floating point format is less in use compared to the long int? If
> Npgsql doesn't support it, any application that uses Npgsql will have this
> limitation anyway. Am I correct?
It looks that way.
64-bit integer representation for datetimes was introduced in 7.3 and
became the default in 8.4, over 7 years ago.
So I guess you won't encounter databases with floating point datetimes
very often these days.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2016-11-15 15:02:42 | Re: Fwd: Mail to be posted in PostgreSQL community |
| Previous Message | Karsten Hilbert | 2016-11-15 11:23:36 | Re: Fwd: Creating multiple instances of postresql on Windows environment |