Re: proposal: PL/Pythonu - function ereport

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: PL/Pythonu - function ereport
Date: 2015-10-09 17:50:52
Message-ID: CAFj8pRBc6cdFRfmfhYWRE_4QHud=GsQzceV+rn8kSCE+FyNqQw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2015-10-09 15:22 GMT+02:00 Peter Eisentraut <peter_e(at)gmx(dot)net>:

> On 10/8/15 6:11 AM, Pavel Stehule wrote:
> > We cannot to raise PostgreSQL exception with setting all possible
> > fields.
>
> Such as? If there are fields missing, let's add them.
>
> > I propose new function
> >
> > plpy.ereport(level, [ message [, detail [, hint [, sqlstate, ... ]]]])
>
> That's not how Python works. If you want to cause an error, you should
> raise an exception.
>

ok,

the patch had two parts - enhancing spi exception and ereport function.
I'll drop implementation of ereport.

Regards

Pavel

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robbie Harwood 2015-10-09 18:04:43 Re: [PATCH v1] GSSAPI encryption support
Previous Message Alvaro Herrera 2015-10-09 16:06:43 Re: pg_ctl/pg_rewind tests vs. slow AIX buildfarm members