Re: Bug in tm2timestamp

From: Michael Meskes <meskes(at)postgresql(dot)org>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bug in tm2timestamp
Date: 2013-03-06 19:50:06
Message-ID: 20130306195006.GB8135@feivel.credativ.lan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 04, 2013 at 05:55:26PM -0300, Alvaro Herrera wrote:
> error codes for the caller to figure out. Maybe we could create a layer
> on top of ereport, that gets both the error message, sqlstate etc, and
> ...

Couldn't we just create ecpg's own version of ereport, that does "the right
thing" for ecpg?

Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
Jabber: michael.meskes at gmail dot com
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2013-03-06 19:57:42 Re: Bug in tm2timestamp
Previous Message Michael Meskes 2013-03-06 19:47:57 Re: Bug in tm2timestamp