Re: ecpg issue - not sending datatype to the backend

From: Michael Meskes <meskes(at)postgresql(dot)org>
To: Mike Aubury <mike(dot)aubury(at)aubit(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: ecpg issue - not sending datatype to the backend
Date: 2008-05-02 15:01:39
Message-ID: 20080502150139.GA18548@feivel.credativ.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 02, 2008 at 02:28:31PM +0100, Mike Aubury wrote:
> Any thoughts ?

As I already explained in private email ecpg uses an untyped statement
and data is always send as text. Of course this could be changed but
only by looking into the backend and asking what datatype this is. I
don't think it's a good idea to just expect people to use the same
datatype in C as in the backend. Keep in mind that this works the other
way round as well. All those people not using pgtypes will probably have
a string to hold the date in C. You can also use date in C but a string
in the database. I don't like the idea of forcing one way to the user,
especially with the current setup working most of the time and the
remaining ones just needing a cast.

Michael

P.S.: Nice move to go to the list in the middle of a discussion. You
could at least give me a chance to answer your email before going
public.

--
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 VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2008-05-02 15:03:32 Re: GUC parameter cursors_tuple_fraction
Previous Message Alvaro Herrera 2008-05-02 14:53:58 Re: Protection from SQL injection