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

Re: ecpg and VARCHAR

From: Michael Meskes <meskes(at)postgresql(dot)org>
To: Dirk Jagdmann <doj(at)cubic(dot)org>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: ecpg and VARCHAR
Date: 2005-08-23 09:31:46
Message-ID: 20050823093146.GA8559@1 (view raw or flat)
Thread:
Lists: pgsql-interfaces
On Sat, Jul 09, 2005 at 11:26:00PM +0200, Dirk Jagdmann wrote:
> I'd like to get some information on VARCHAR types with ecpg. If I 
> declare a VARCHAR without any size information I get a compilation error 
> from my gcc 3.4.4:
> ...
> Now I suppose this negative declaration should have initialized an empty 
> array and the generated sql code then allocates the space as needed?

Well, actually no. You just found a way to declare a pointer to a
varchar that wasn't tested for. I will fix this test. Unfortunately it
only means that you will get an error message from ecpg. It simply is
not implemented yet. Should be easy to do but my spare time is rare at
the moment.

> If I declared the VARCHAR with a size everything works fine. However I'd 
> like to know if the characters in the array contain a trailing 0 or if I 
> have to set this explicitely?

No. With char it may, but with varchar it does not.

> And then I'd like to know which is the preferred way to retrieve "text" 
> columns which contain arbitrary length texts with ecpg?

How about 'char *'? Just make sure the pointer is NULL and you free it
after use.

Michael
-- 
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes(at)jabber(dot)org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!

In response to

pgsql-interfaces by date

Next:From: Michael MeskesDate: 2005-08-23 09:53:38
Subject: Re: ecpg: arrays and nulls
Previous:From: Michael MeskesDate: 2005-08-23 07:40:36
Subject: Re: ECPG and escape strings

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