--- Michael Fuhr <mike(at)fuhr(dot)org> wrote:
> For data in text format, the value returned by
> PQgetvalue is a
> null-terminated character string representation of
> the field
> value. For data in binary format, the value is in
> the binary
> representation determined by the data type's
> typsend and typreceive
> But you should only need to do this if you need
> query results in
> binary format. Do you?
Actually, what I really needed is a timestamp data in either time_t or
struct tm format so that my application could easily manipulate the
data. If the data recieved is in string format, it would be a hassle
to manually parse the string just to convert it to struct tm.
Moreover, I'm not so sure but, if nls is supported, the query to
timestamp data might return the string formatted in another language
which would add more complications to parsing.
> Unless you request results in binary format all
> values will be
> returned as text strings. What happened when you
> tried it? Are
> you requesting results in binary format?
When I tried getting the results in binary format, I get some value
which I have no idea how to parse, however, PostgreSQL has functions
(timestamp_recv) for converting timestamp data to struct pg_tm (which
I need) somewhere in timestamp.c/.h and it uses j2date which is
located in datetime.c/.h (both are located at \src\utils\). The
problem with using these is that they are (probably) part of the
backend. Could libpq be manipulated so that it includes those
functions (it could probably share that same code that that it's
synched with the backend format)?
pgsql-interfaces by date
|Next:||From: Rob Marjot||Date: 2007-03-12 21:22:28|
|Subject: pgsql on a PDA running Microsoft CE|
|Previous:||From: Jeff Davis||Date: 2007-03-10 00:56:40|
|Subject: Re: DBD-pg - server closed the connection unexpectedly|