Neil Conway <[EMAIL PROTECTED]> writes:
> "Jeff Post" <[EMAIL PROTECTED]> wrote:
>> The best way that I can think to describe this is that views are not added
>> as candidates of possible line completions in psql.
> On my end, that doesn't seem to be the case (running a build of CVS
> that is few
On Fri, 24 May 2002 17:16:28 -0700
"Jeff Post" <[EMAIL PROTECTED]> wrote:
> The best way that I can think to describe this is that views are not added
> as candidates of possible line completions in psql.
> So if I have a view with the name org_details and a table with the name
> organizations an
> > lower/upper-casing is driven by locale, not encoding.
> >
> > Unfortunately you didn't mention anything about your locale setup...
>
> The server locale is en_US.UTF-8. (At least I set it up as such when
> installing PostgreSQL; I know no way to verify.) The server version is 7.2.1,
> runnin
hi all,
with latest cvs version of pg i've found this problem:
ns:/tmp> createdb gino
CREATE DATABASE
ns:/tmp> psql gino
Welcome to psql, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help on internal slas
see attachment.
--
Chris Traylor
If PostgreSQL failed to compile on your computer or you found a bug that
is likely to be specific to one platform then please fill out this form
and e-mail it to [EMAIL PROTECTED]
To report any other bug, fill out the form below and e-mail it to
[EMAIL PR
On Sat, May 25, 2002 at 12:56:06AM -0400, Tom Lane wrote:
> [EMAIL PROTECTED] writes:
> > The string case manipulation functions lower(), upper(), & initcap()
> > have no effect on non-ASCII characters in the argument, such as �, �,
> > �, �, etc. ASCII chars in the argument are properly up- or
The best way that I can think to describe this is that views are not added
as candidates of possible line completions in psql.
So if I have a view with the name org_details and a table with the name
organizations and I try select * from org the completion is
organizations not a list of organizatio
[EMAIL PROTECTED] writes:
> I saw a artiche what say that in 7.2 PostgreSQL version, the resource of create a
>user with NOCREATETABLE was ready to use.
I don't know where you saw that, but it has nothing to do with reality.
regards, tom lane
---
Marcia Abade ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
NOCREATETABLE
Long Description
I saw a artiche what say that in 7.2 PostgreSQL version, the resource of create a user
with NOCREATETABLE was ready to use.
I´m trying
Andrew McMillan <[EMAIL PROTECTED]> writes:
> Reading between a few lines I got the impression that the manual
> suggested something like:
> CREATE or REPLACE myfunc( tablename%ROWTYPE ) RETURNS ...
> When I finally got my function working, I found I had:
> CREATE or REPLACE myfunc( tablename ) RE
--On mardi 21 mai 2002 10:19 -0400 Tom Lane <[EMAIL PROTECTED]> wrote:
> Mathieu Arnold <[EMAIL PROTECTED]> writes:
>> when I dump my database, in the dump file, the aggregate becomes :
>
>> CREATE AGGREGATE first ( BASETYPE = text, SFUNC = first_cat, STYPE =
>> text, INITCOND = '' );
>
> Ooop
I recently referred to the manual (section 23.3) to work out how to
write a PL/PgSQL function that accepted a row as a parameter.
Reading between a few lines I got the impression that the manual
suggested something like:
CREATE or REPLACE myfunc( tablename%ROWTYPE ) RETURNS ...
When I finally g
12 matches
Mail list logo
