Charles Tassell ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
Can't use NULL in IN conditional?
Long Description
I don't know if this is a "feature" that comes alogn with NULL values, or somethign
I'm doing wrong, but I can'
[EMAIL PROTECTED] writes:
> -- This works
> SELECT type_id, code FROM product_types WHERE code = '0A' OR code = NULL;
> -- This doesn't
> SELECT type_id, code FROM product_types WHERE code IN ('OA', NULL);
"code = NULL" is not legal SQL --- or at least, the standard's
interpretation of it is not
Quoting Stu Coates <[EMAIL PROTECTED]>:
> I think that I've found a little bug in the 7.1beta1 JDBC drivers.
> Attached is a simple test case which produces the problem on my setup
> (LinuxPPC 2000, on Apple PowerMac G3-400Mhz, 512MB). It would seem that
> the drivers and/or the DBMS has a probl
On Monday 11 December 2000 10:51, Tom Lane wrote:
> [EMAIL PROTECTED] writes:
> > -- This works
> > SELECT type_id, code FROM product_types WHERE code = '0A' OR code = NULL;
> > -- This doesn't
> > SELECT type_id, code FROM product_types WHERE code IN ('OA', NULL);
>
> "code = NULL" is not legal S
Since it's probably a "special case" I'd feel it good software engineering
practice to make that fact explicit anyway.
For example:
SELECT type_id, code FROM product_types WHERE code IN ('0A', 'F3', '99')
OR code IS NULL;
I don't know how that would affect the speed but it might be the cle
"Robert B. Easter" <[EMAIL PROTECTED]> writes:
> What you are saying agrees with things I've read elsewhere, and a little
> definition/note that I wrote on my "Databasing" Terms page:
> three-valued logic:
> a logic system that employs TRUE, FALSE, and UNKNOWN. NULL values introduce
> UNKNOWN in
On Monday 11 December 2000 12:34, Tom Lane wrote:
> Three-valued logic is perfectly straightforward if you keep in mind the
> interpretation of NULL/UNKNOWN: "I don't know if this is true or false".
> Thus:
>
> NOT unknown => unknown
>
> false AND unknown => false (it can't possibly
Hi There,
I have production systems running postgres for
24x7x365. But suddenly it stops serving the requests
but the postmaster does not die. I cant do select or
even say pgsql until i kill postmaster
clear shared memory segments and restart it again. for
all the forth coming requests it s
Dronamraju Rajesh <[EMAIL PROTECTED]> writes:
> database:- Postgres 6.5.2 ( pl dont suggest to upgrade
> to 7.0.2. once this problem is solved. then i can do
> testing of my app with postgres 7.0.2)
If you update to 7.0.3, you'll probably find this problem
goes away. It sounds to me like you are
thanks tomBut strange thing is that my database
has only 15 tables totally...which are very small
too...
so how would be the way of me reaching to 1000
tables???
and why do i get an error message "sorry too many
clients" ???
Regards
Rajesh
--- Tom Lane <[EMAIL PROTECTED]> wrote:
> Dronamra
10 matches
Mail list logo
