Tom Lane wrote:
>Marvin Bellamy <marvin.bellamy@innovision.com> writes:
>
>
>>I'm trying to read/write timestamps as binary data, but I'm getting
>>garbage. It looks like there are 8 bytes of timestamp data (if I read
>>the headers correctly), which I had assumed was the time in millis from
>>the PostgreSQL epoch, but my values are way off.
>>
>>
>
>Are you using integer datetimes? It should be either a float8 measured
>in seconds, or an int8 measured in microseconds since the epoch.
>
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
>
>
I've been treating the timestamp as an integer, not a double. What's a
good way to deal with double/float byte ordering when reading/writing
data from Windows applications?
--
Marvin Keith Bellamy
Software Engineer
Innovision Corporation
913.438.3200
