The Hermit Hacker <[EMAIL PROTECTED]> writes:
> duplicated index entry found, CHARACTER STRINGS LENGTH
> duplicated index entry found, LENGTH CHARACTER STRINGS
> duplicated index entry found, SUBSTRING
> duplicated index entry found, SUBSTRING
> 4 entries ignored...
Yeah, I've been seeing that for
Folks,
Am I missing something here? We're preparing for migration, but I can't find
anywhere a centralized list of the new error messages. Is it in the source
somewhere? If so, can we add it to the documentation?
--
-Josh Berkus
Aglio Database Solutions
San Francisco
-
Josh Berkus <[EMAIL PROTECTED]> writes:
> Am I missing something here? We're preparing for migration, but I
> can't find anywhere a centralized list of the new error messages. Is
> it in the source somewhere? If so, can we add it to the
> documentation?
You could make one by running gettext ---
Tom,
> Or were you looking for src/include/utils/errcodes.h ?
More or less.
The issue is that many projects have internal code to handle PG error messages
by parsing them for certain text. The overhaul of message handling is going
to break that code; users need to know what the new messages
The issue is that many projects have internal code to handle PG error
messages
by parsing them for certain text. The overhaul of message handling
is going
to break that code; users need to know what the new messages and/or
codes are
before migrating.
I concur, I have such an application and it
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> Or were you looking for src/include/utils/errcodes.h ?
> I think we should put such a list in the documentation, at least for those
> error codes that we have really assigned.
I have no objection to that. I have doubts about the
The point of including the message texts is
for people supporting various versions who
are looking directly at the message texts
for earlier versions.
This also allows them to upgrade the error
handling to use the new error codes instead
of relying on the message text (which is what
we want).
ele
Tom Lane writes:
> The Hermit Hacker <[EMAIL PROTECTED]> writes:
> > duplicated index entry found, CHARACTER STRINGS LENGTH
> > duplicated index entry found, LENGTH CHARACTER STRINGS
> > duplicated index entry found, SUBSTRING
> > duplicated index entry found, SUBSTRING
> > 4 entries ignored...
>
The issue is that many projects have internal code to handle PG error
messages
by parsing them for certain text. The overhaul of message handling
is going
to break that code; users need to know what the new messages and/or
codes are
before migrating.
I concur, I have such an application and it
Tom Lane writes:
> Or were you looking for src/include/utils/errcodes.h ?
I think we should put such a list in the documentation, at least for those
error codes that we have really assigned.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)--
10 matches
Mail list logo
