Excerpts from Susanne Ebrecht's message of vie may 20 09:04:26 -0400 2011:
> On 20.05.2011 13:56, Tom Lane wrote:
> >>* Should we allow non-ASCII characters in general source files?
> > Prefer "no" here.
>
> I only see two reasons for non-ASCII signs in English.
> Either it is a foreign na
Le 05/20/2011 06:53 PM, Alvaro Herrera a écrit :
> Excerpts from Derrick Rice's message of vie may 20 12:35:24 -0400 2011:
>> On Fri, May 20, 2011 at 12:18 PM, Guillaume Lelarge
>> wrote:
>>
>>> Well, for a specific object, any superuser, the database owner, the
>>> schema owner, and the object own
Excerpts from Derrick Rice's message of vie may 20 12:35:24 -0400 2011:
> On Fri, May 20, 2011 at 12:18 PM, Guillaume Lelarge
> wrote:
>
> > Well, for a specific object, any superuser, the database owner, the
> > schema owner, and the object owner could drop the object. This is not a
> > vulnerabi
On Fri, May 20, 2011 at 12:18 PM, Guillaume Lelarge
wrote:
> Well, for a specific object, any superuser, the database owner, the
> schema owner, and the object owner could drop the object. This is not a
> vulnerability.
>
It is not documented clearly. Any information not made clear is an
opportu
Le 05/20/2011 05:42 PM, Derrick Rice a écrit :
> According to
>
> http://www.postgresql.org/docs/9.0/interactive/sql-droptable.html
>
> "DROP TABLE removes tables from the database. Only its owner can drop a
> table."
>
> In fact, the schema owner can drop the table, which is clearly stated here
According to
http://www.postgresql.org/docs/9.0/interactive/sql-droptable.html
"DROP TABLE removes tables from the database. Only its owner can drop a
table."
In fact, the schema owner can drop the table, which is clearly stated here:
http://www.postgresql.org/docs/9.0/interactive/sql-dropschem
On 20.05.2011 13:56, Tom Lane wrote:
* Should we allow non-ASCII characters in general source files?
Prefer "no" here.
I only see two reasons for non-ASCII signs in English.
Either it is a foreign name of e.g. a person
or it is a word that English took from French like in déjà vu.
For t
On 20.05.2011 14:08, Tom Lane wrote:
I'm pretty sure this is documented somewhere, but perhaps not in the
place where Grzegorz looked for it ...
Hehe - that was my intention too. I looked through the Tutorial and
through some other chapters - but I couldn't find a hint.
Susanne
--
Susanne Eb
http://www.postgresql.org/docs/9.0/static/queries-table-expressions.html
http://www.postgresql.org/docs/9.0/static/sql-select.html
Respectively:
"Finally, NATURAL is a shorthand form of USING: it forms a USING list
consisting of all column names that appear in both input tables. As
with USING, th
Excerpts from Tom Lane's message of vie may 20 07:56:58 -0400 2011:
> Peter Eisentraut writes:
> > * Should we consistently use entities for encoding non-ASCII
> > characters in SGML? Or use LATIN1 freely?
>
> I think we previously discussed this and agreed that all non-ASCII in
>
Susanne Ebrecht writes:
> PostgreSQL even is so intelligent - that when you say:
> $ createdb "tEst" - it will ignore the quotes - you will get database
> named tEst and not
> named "tEst".
Not true. The reason you don't get quotes there is that the shell
stripped them off. Try '"tEst"' ...
T
Peter Eisentraut writes:
> * Should we consistently use entities for encoding non-ASCII
> characters in SGML? Or use LATIN1 freely?
I think we previously discussed this and agreed that all non-ASCII in
the SGML docs should be written as entities. The existence of
violations of tha
On 19.05.2011 22:15, Robert Haas wrote:
On Wed, May 4, 2011 at 12:05 PM, Grzegorz Szpetkowski
wrote:
Hi,
I think that createuser/drouser reference documentation could be
enhanced for username param. There is:
"createuser is a wrapper around the SQL command CREATE ROLE. There is
no effective
Hello Peter,
On 19.05.2011 23:49, Peter Eisentraut wrote:
So, some questions:
* Should we consistently use entities for encoding non-ASCII
characters in SGML? Or use LATIN1 freely?
* Should we allow/use non-ASCII characters in the release notes?
* What encoding sh
14 matches
Mail list logo