> > \h select in psql says (among other things)
> > [ { UNION | INTERSECT | EXCEPT [ ALL ] } select ]
> > I think it should read
> > [ { UNION | INTERSECT | EXCEPT } [ ALL ] select ]
>
> I agree. Bruce ("Mr. Backslash" :) are you planning on picking this up?
Done. :-)
--
Bruce Momji
>
> \h select in psql says (among other things)
>
> [ { UNION | INTERSECT | EXCEPT [ ALL ] } select ]
>
> I think it should read
>
> [ { UNION | INTERSECT | EXCEPT } [ ALL ] select ]
>
> (the SQL reference says the same thing as psql)
Good catch! Hard to imagine how we missed seeing
"Andras Belokosztolszki" <[EMAIL PROTECTED]> writes:
> When I use 2 or more triggers (body written in C) with trigger parameters,
> triggered within the same psql connection the backend crashes randomly.
It's hard to tell for sure from your incomplete example, but I wonder
whether you are sometim
Wiktor Rzeczkowski <[EMAIL PROTECTED]> writes:
> (select k.bib from kw k where k.kword='concept')
> intersect
> (select k.bib from kw k where k.kword='of')
> intersect
> (select k.bib from kw k where k.kword='god');
> bib
> ---
> (0 rows)
> // THIS GIVES AN INCORRECT RESULT - see the following /
[EMAIL PROTECTED] writes:
> Trying to compile postgresql under solaris 2.6 configure stops
> claiming about an unknown symbol "optreset". I wasn't able to fix the
> problem.
You misread it: the log shows that it's the test after the optreset one
that is failing. That test is just trying to compi
> \h select in psql says (among other things)
> [ { UNION | INTERSECT | EXCEPT [ ALL ] } select ]
> I think it should read
> [ { UNION | INTERSECT | EXCEPT } [ ALL ] select ]
I agree. Bruce ("Mr. Backslash" :) are you planning on picking this up?
- Thomas
-
\h select in psql says (among other things)
[ { UNION | INTERSECT | EXCEPT [ ALL ] } select ]
I think it should read
[ { UNION | INTERSECT | EXCEPT } [ ALL ] select ]
(the SQL reference says the same thing as psql)
--
Alvaro Herrera ()
"La virtud es el justo medio entre dos defectos
On Friday 19 Oct 2001 9:33 pm, Joel Burton wrote:
> On Fri, 19 Oct 2001, Chris Storah wrote:
> > MS SQL is set to quote all identifiers so the queries are sent in the
> > ...
Sorry about that, I wasn't clear about the quoting.
MS SQL was set to quote all identifiers so that I could force the "TEST
Hello,
The following exemplifies a problem with Postgresql 7.1.3 that I have
recently encountered. I have an impression that a similar problem was
addressed in version 7.1.3 but, as it seems, not completely.
+
(select k.bib from kw k where k.k
Thanks for your response. This is the first and only install of PG on this
box, so that sounds a bit strange. I have no other installations the check
for, unless one comes standard with Red Hat 6.0.
I have updated the PGLIB setting (to /usr/local/pgsql/lib) and now get this
message:
* * *
initdb
When I use 2 or more triggers (body written in C) with trigger parameters,
triggered within the same psql connection the backend crashes randomly.
Previous triggers execute without any problems, the triggers, which should
be fired do not even start.
Postgresql version 7.1.3 (had the same problem
Hello Sir,
I am working as DBA in both Oracle and MSSQL Server.
I would like to make the postgresql server in my machine.
So please send the details how to install in Windows.
I have Windows NT and Windows 2000.
I need to know the Server part and Client part intallation also in Windows.
Plse sen
Holger Mittewald ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
Can't compile PostgreSQL 7.1.3 with Solaris 2.6
Long Description
Trying to compile postgresql under solaris 2.6 configure stops claiming about an
unknown symbol
13 matches
Mail list logo
