[EMAIL PROTECTED] writes:
> sql-# \a?
> Output format is aligned.
> \a: extra argument '?' ignored
> Segmentation fault
> $ psql
7.1.1? If so, this is a minor bug that slipped into psql for about two
days at just the wrong time :-(. Update to 7.1.2.
regards, tom lane
-
[EMAIL PROTECTED] writes:
> View definition: SELECT zz.ff AS "user", zz.ss AS num FROM zz;
> View definition: SELECT zz.ff AS user1, zz.ss AS num FROM zz;
> Why in the first case column has name "user" (with '"') ?
USER is a keyword. It happens not to be reserved, so you can use it for
an AS n
Hi,
developing in MFC/Visual Studio 6 I've encountered a strange problem
in last version of ODBC Driver (actually 07_01_0005). Each time a SQL
error occours, the istructions TRY/ CATCH doesn't report the error
string: the CDBException ' member m_strError is empty
Follows an example:
// MFC C++
On Thu, 14 Jun 2001 [EMAIL PROTECTED] wrote:
> Basil A. Evseenko ([EMAIL PROTECTED]) reports a bug with a severity of 3
> The lower the number the more severe it is.
>
> Short Description
> Strange CREATE VIEW behavior??
>
> Long Description
> createdb test
> psql test
>
> test=# create table
Paul Mamin ([EMAIL PROTECTED]) reports a bug with a severity of 4
The lower the number the more severe it is.
Short Description
Segmentation fault in psql
Long Description
$ psql
Welcome to psql, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help wi
Basil A. Evseenko ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
Strange CREATE VIEW behavior??
Long Description
createdb test
psql test
test=# create table zz(ss int, ff varchar);
test=# create view ff2 as select ff as user,
[EMAIL PROTECTED] writes:
> Since the difference set bar - foo is nonempty, the above
> should yield one or more rows. However, the presence of a null
> in foo.col1 (tests 3 and 8 below) yields zero rows, even where
> the difference set has rows with no null entries (see test 2).
This is the spe
Vinod Kurup <[EMAIL PROTECTED]> writes:
> Will this fix then be placed in the next 7.1.x release as well?
Yes, if there is one.
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://w
Dr M J Carter ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
"WHERE col NOT IN" yields falsely empty result.
Long Description
Consider
SELECT * FROM bar WHERE col2 NOT IN (SELECT col1 FROM foo)
where tables foo and b
