I have moved the text about duplicate constraints to the top of the
information schema section because it affects several tables (applied
patch attached). I could not figure out how to get the actual error
concept to the front of the paragraph.
---
Hey Alvaro,
2011/2/21 Alvaro Herrera
> Excerpts from Dmitriy Igrishin's message of dom feb 20 06:19:19 -0300 2011:
>
> > Better, undoubtedly.
> > Another alternative is just "server". Why? Well, for consistency, e.g.
> with
> > http://www.postgresql.org/docs/9.0/static/errcodes-appendix.html
> >
Excerpts from Dmitriy Igrishin's message of dom feb 20 06:19:19 -0300 2011:
> Better, undoubtedly.
> Another alternative is just "server". Why? Well, for consistency, e.g. with
> http://www.postgresql.org/docs/9.0/static/errcodes-appendix.html
> Here you may see phrase "All messages emitted by the
Alvaro Herrera wrote:
> Excerpts from Bruce Momjian's message of lun feb 21 00:21:37 -0300 2011:
> >
> > Applied.
>
> I think this paragraph is a bit strange:
>
> + This chapter describes how to create and manage roles.
> + More information about the effects of privileges on various database
>
Excerpts from Bruce Momjian's message of lun feb 21 00:21:37 -0300 2011:
>
> Applied.
I think this paragraph is a bit strange:
+ This chapter describes how to create and manage roles.
+ More information about the effects of privileges on various database
+ objects can be found in .
Note that
Hello,
When constraint names are generated by postgresql, ISTM that the software
is free to choose them so they could be chosen non ambiguous per schema.
We do that already. See ChooseConstraintName and ChooseRelationName.
Very good news! I had not noticed that change yet. No more multiple
On 21 February 2011 03:21, Bruce Momjian wrote:
>
> Applied.
>
> ---
>
> Bruce Momjian wrote:
>> Kevin Grittner wrote:
>> > Thom Brown wrote:
>> > > On 12 August 2010 00:05, Thom Brown wrote:
>> > >> I noticed that there are
