On Jul 20 08:21, Dan Strömberg wrote:
I would like to know if it is possible to find out the datatypes in the
resultset of a query or a set returning
function without actually executing them ?
As Tom mentioned, there's support for this feature in the protocol
level, but I don't know any API
On 21.07.2006 11:12 Volkan YAZICI wrote:
As Tom mentioned, there's support for this feature in the protocol
level, but I don't know any API supports this yet.
I think if you run a query like the suggested one (or SELECT ... WHERE
1=2) the JDBC API will provide the necessary information via
Volkan YAZICI wrote:
On Jul 20 08:21, Dan Strömberg wrote:
I would like to know if it is possible to find out the datatypes in the
resultset of a query or a set returning
function without actually executing them ?
As Tom mentioned, there's support for this feature in the protocol
level, but
On Jul 21 09:02, Jacob Coby wrote:
Volkan YAZICI wrote:
As Tom mentioned, there's support for this feature in the protocol
level, but I don't know any API supports this yet. However, here's a
patch that adds Describe functionality for Prepared Statements and
Cursors to libpq:
On Fri, Jul 21, 2006 at 04:14:52PM +0300, Volkan YAZICI wrote:
On Jul 21 09:02, Jacob Coby wrote:
Volkan YAZICI wrote:
As Tom mentioned, there's support for this feature in the protocol
level, but I don't know any API supports this yet. However, here's a
patch that adds Describe
Martijn van Oosterhout wrote:
On Fri, Jul 21, 2006 at 04:14:52PM +0300, Volkan YAZICI wrote:
On Jul 21 09:02, Jacob Coby wrote:
Volkan YAZICI wrote:
As Tom mentioned, there's support for this feature in the protocol
level, but I don't know any API supports this yet. However, here's a
patch
On Jul 21 03:34, Martijn van Oosterhout wrote:
Really, I would have thought the PHP function would map directly to the
libpq PQftype() function. Although libpq returns the OID whereas the
PHP function returns the type. But I don't think that's what the
original user asked for given you need a
On Fri, Jul 21, 2006 at 05:07:08PM +0300, Volkan YAZICI wrote:
AFAICS, that's not possible with current parsing capabilities. See
related lines in
fe-protocol3.c:pqParseInput3()
102 /*
103 * Can't process if message body isn't all here yet.
104 */
AM
To: Volkan YAZICI
Cc: Jacob Coby; Dan Strömberg; pgsql-general@postgresql.org
Subject: Re: [GENERAL] Column info without executing query
On Fri, Jul 21, 2006 at 05:07:08PM +0300, Volkan YAZICI wrote:
AFAICS, that's not possible with current parsing capabilities. See
related lines in
fe
On Jul 21 04:25, Martijn van Oosterhout wrote:
On Fri, Jul 21, 2006 at 05:07:08PM +0300, Volkan YAZICI wrote:
AFAICS, that's not possible with current parsing capabilities. See
related lines in
fe-protocol3.c:pqParseInput3()
102 /*
103 * Can't process if
On Fri, Jul 21, 2006 at 05:47:32PM +0300, Volkan YAZICI wrote:
Did you see my comment about get partial result sets from libpq. for
asyncronous queries you can run PQftype as soon as you've received and
parsed the T record
We can run PQftype() on what, conn-result? (We can't use a
I found pg_prog.prorettype in the system catalogs , is it possible to
use that to find the resultset datatypes of a
set returning function ?
Anyway , maybe the odbc driver will work by using SQLDescribecol()
without executing it ?!
I found something in the archives where someone suggests that
Hi List !
I would like to know if it is possible to find out the datatypes in the
resultset of a query or a set returning
function without actually executing them ?
I know there is something like that in MS SQL Server where you can use
the SET FMTONLY option and only
get the column
=?ISO-8859-1?Q?Dan_Str=F6mberg?= [EMAIL PROTECTED] writes:
I would like to know if it is possible to find out the datatypes in the
resultset of a query or a set returning
function without actually executing them ?
You could always do SELECT ...whatever ... LIMIT 0. Also, at the
protocol
Dan Strömberg wrote:
Hi List !
I would like to know if it is possible to find out the datatypes in
the resultset of a query or a set returning
function without actually executing them ?
Well for result sets of queries on tables there is always the
pg_attribute catalog table.
See:
15 matches
Mail list logo
