Andrew Dunstan wrote:
> David Fetter wrote:
>>> Maybe we should fix our C sample trigger, from which this was taken.
>> Yes :)
>> Does the attached have the right error code?
>> - elog(ERROR, "trigf: not called by trigger manager");
>> + ereport(ERROR,
>> + (error(TRIGGERED_DATA_CHANGE_VIOLATION),
>> + errmsg("trigf: not called by trigger manager")));
> Not sure that's appropriate, but I can't see anything else that is
> very appropriate either.
The plpgsql code uses errcode(ERRCODE_FEATURE_NOT_SUPPORTED) for this
situation, so I guess we should be consistent with that.
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2008-10-29 20:43:06|
|Subject: Re: PostgreSQL network discovery |
|Previous:||From: Andrew Dunstan||Date: 2008-10-29 20:20:15|
|Subject: Re: minimal update|