2011/7/28 Florian Pflug <f...@phlo.org>: > On Jul27, 2011, at 23:20 , Pavel Stehule wrote: >> this is a refreshed patch. Only constraints and RI is supported now. >> There is about 1000 ereport calls, where a enhanced diagnostics should >> be used, but probably we don't modify all in one time. > > I wonder if it wouldn't be better to have something like the machinery > around ErrorContextCallback to fill in the constraint details. You'd then > only need to modify the places which initiate constraint checks, instead > of every single ereport() in the constraint implementations. > > Just a wild idea, though - I haven't check whether this is actually > feasible or no.
I though about this too, but sometimes is relative difficult to specify a fields before exception -- see a ri_triggers part. TABLE_NAME and TABLE_SCHEMA should not contains a name of processed table, but name of error, that is related to error. It can be different. But if we would to use a enhanced errors for "in" functions, then some injection into ErrorContextCallback should be necessary - but again - the these fields are no related to function's scope - so it mean a more manipulation with ErrorContext. Regards Pavel Stehule > > best regards, > Florian Pflug > > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers > -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers