From: | Mihai RUSU <dizzy(at)roedu(dot)net> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: libpq API for PQcmdTuples() |
Date: | 2004-03-04 13:05:37 |
Message-ID: | Pine.LNX.4.58L0.0403041504250.14907@ahriman.bucharest.roedu.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 3 Mar 2004, Bruce Momjian wrote:
> I think the reason it is a string is mostly historical. You should be
> find just converting it to an int.
Ok thanks! However, its pretty dumb because probably libpq internally does
the int -> str conversion and then I do the reverse... A new libpq
function returning the numerical value would be nice :)
- --
Mihai RUSU Email: dizzy(at)roedu(dot)net
GPG : http://dizzy.roedu.net/dizzy-gpg.txt WWW: http://dizzy.roedu.net
"Linux is obsolete" -- AST
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFARymlPZzOzrZY/1QRAiLwAJ4pL8TkFisF/W97/fABfqyVBQQWdwCfSrFU
QPhQwizZQSx08iT+POG1tMY=
=L1PG
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2004-03-04 13:08:57 | Re: gist index build produces corrupt result on first access |
Previous Message | mbc | 2004-03-04 12:35:42 | clarification of postgres limitations |