DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:user-agent:mime-version:to:cc:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	b=W1M8X7jZo5dd17zpfwDbCrKnzqmQkFwmVX/pR8pgovxr7LAtistw/aNkkg1LJ+czBx
	fkV6sihVY6NjusEL8SqxJtQ45j5qTfl/8XdYrs2zOL15pOgz8WEPKpGlJc/iRpuaN7OZ
	J1LLEweY8GdqfWoXcuAUe0lqHzwf+UxWrKHP0=
Message-ID: <4C1B28E1.2020700@gmail.com>
Date: Fri, 18 Jun 2010 17:05:53 +0900
From: Satoshi Nagayasu <satoshi.nagayasu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja;
	rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Mark Richardson <markmapo@yahoo.com>
CC: pgsql-interfaces@postgresql.org
Subject: Re: ECPG Documentation Improvement
References: <695459.74507.qm@web53308.mail.re2.yahoo.com>
In-Reply-To: <695459.74507.qm@web53308.mail.re2.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Mark,

Thanks for the comments.

On 2010/06/18 4:27, Mark Richardson wrote:
> Here's some info that I found...
> For conversion of Sybase .pc files to postgres .pgc files, you have to
> parse the .pc file and change from sybase format to postgres format. We
> used a simple script but here's what we changed the following (sybase is
> first column, postgres is second - quotes are used just to indicate the
> entire string, you don't need them in the search/replace)

As you mentioned, I feel the embeded SQL technology has
many compatibility challenges to port applications.
So now I'm thinking how we can hold such compatibility
tips or tricks in the manual.

I'm interested in having the "Compatibility" section
to gather compatibility information which depends on
several RDBMSes, like "Informix compatibility mode" section.
If it could be helpful, I will try it.

I have to work on SQLDA stuffs to clarify its usage,
because I heard that the PostgreSQL SQLDA is not compatible
with Oracle's one, it's compatible with others
(DB2? Sorry if it's wrong).

Thus, the PostgreSQL ECPG is currently a mixture of several
RDBMSes, so I want to clarify the spec and its compatibility.
I guess it could be helpful for application developers. :)

> I also looked up the boolean type for ecpg, the problem is in postgres
> 8.0.1 (maybe later)
> postgresql/src/interfaces/ecpglib/execute.c line 775 (case ECPGt_bool)
> the line was

I will check this, and modify the manual if we need.

Regards,
-- 
NAGAYASU Satoshi <satoshi.nagayasu@gmail.com>