Skip site navigation (1) Skip section navigation (2)

Re: row description, protocol 3

From: John DeSoi <desoi(at)pgedit(dot)com>
To: Josh Close <narshe(at)gmail(dot)com>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: row description, protocol 3
Date: 2006-03-01 13:01:25
Message-ID: 3F471D6F-68A9-4AC9-BB48-9E4C1C6AD8C0@pgedit.com (view raw or flat)
Thread:
Lists: pgsql-interfaces
On Feb 28, 2006, at 8:13 PM, Josh Close wrote:

> So, after a select is done, and I get a row description back, I  
> need to do another query to find out what the actual type was?
>
> I'm writing a dataprovider, so I need to map the types back to .NET  
> types. It seems kinda odd that you'd have to do a second query to  
> find out the type.


The majority will correspond to fixed types in PostgreSQL. I just  
used this type list to build a program that parses the data into the  
native type of the application. Or if you just need to know the name  
of the type, build some kind of lookup table in the application. You  
could also do the lookup once and then cache the result.

John



John DeSoi, Ph.D.
http://pgedit.com/
Power Tools for PostgreSQL


In response to

pgsql-interfaces by date

Next:From: Bruce MomjianDate: 2006-03-06 15:35:51
Subject: Re: LibPqEasy, binary cursor, x86-64, fetch(int4) problem?
Previous:From: Josh CloseDate: 2006-03-01 01:13:39
Subject: Re: row description, protocol 3

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group