Robert Haas writes:
> On Mon, May 3, 2010 at 1:01 PM, Tom Lane wrote:
>> My own preference for what to do about this is to leave the primary
>> message texts alone and add additional error-message fields for object
>> name and schema. This would address the need without making messages
>> uglier
On Mon, May 3, 2010 at 1:01 PM, Tom Lane wrote:
> My own preference for what to do about this is to leave the primary
> message texts alone and add additional error-message fields for object
> name and schema. This would address the need without making messages
> uglier for the large fraction of
"Greg Sabino Mullane" writes:
>> We're really not going to address this type of complaint on a
>> one-error-message-at-a-time basis. See prior discussions --- a more
>> realistic (and standards compliant) approach will probably involve
>> adding fields to the verbose form of the error message.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> ERROR: invalid input syntax for integer: "abc"
> CONTEXT: COPY alpha.foo, line 1, column a: "abc"
> We're really not going to address this type of complaint on a
> one-error-message-at-a-time basis. See prior discussions --- a more
> reali
Greg Sabino Mullane writes:
> Use case: when running a process that populates many inherited
> tables across schemas, having one fail gives the unhelpful
> error message:
> ERROR: invalid input syntax for integer: "abc"
> CONTEXT: COPY foo, line 1, column a: "abc"
> Unhelpful because "foo" d
Use case: when running a process that populates many inherited
tables across schemas, having one fail gives the unhelpful
error message:
ERROR: invalid input syntax for integer: "abc"
CONTEXT: COPY foo, line 1, column a: "abc"
Unhelpful because "foo" does not uniquely identifies the table
or
