PROTECTED]
CC: [EMAIL PROTECTED]
Subject: RE: comparing null values
Date: Thu, 30 Jan 2003 13:15:33 -0600
Gary,
Null has no value. It can't be like or not like anything. If you want to
see the null you'll need to add OR IS NULL to your Where clause.
Jerry Whittle
ASIFICS DBA
NCI Information Systems
Author: Sony kristanto [EMAIL PROTECTED]
Date: 1/30/2003 6:22 PM
Hi Gary,
I wonder why you didn't use :
select * from tester2 where whatever is null;
Null values is extremely empty.
Rgrds,
Sony
-Original Message-
From: Gary Jackson [SMTP:[EMAIL PROTECTED]]
Sent: Friday, January
Can anyone explain why it is that I seem unable to use 'like' and 'not like'
on columns containing null values. (I am unable to find information
regarding this on MetaLink.)
For example:
SQL select * from tester2;
COL1 COL2 WHATEVER
11STUFF
22STUFF
33
4
PROTECTED]
Sent: Thursday, January 30, 2003 12:41 PM
Can anyone explain why it is that I seem unable to use 'like' and 'not
like'
on columns containing null values. (I am unable to find information
regarding this on MetaLink.)
For example:
SQL select * from tester2;
COL1 COL2 WHATEVER
Title: RE: comparing null values
Gary,
Null has no value. It can't be like or not like anything. If you want to see the null you'll need to add OR IS NULL to your Where clause.
Jerry Whittle
ASIFICS DBA
NCI Information Systems Inc.
[EMAIL PROTECTED]
618-622-4145
-Original
Title: RE: comparing null values
Gary I think this goes back to the classic definition of NULL. NULL means unknown value. Therefore you can't say anything definite about the value. So it is not equal to anything or like anything, period. It is IS NULL from a SQL perspective.
HTH
containing null values. (I am unable to find information
regarding this on MetaLink.)
For example:
SQL select * from tester2;
COL1 COL2 WHATEVER
11STUFF
22STUFF
33
44
SQL select * from tester2 where whatever not like '%STU%';
no rows selected
My question
'
on columns containing null values. (I am unable to find information
regarding this on MetaLink.)
For example:
SQL select * from tester2;
COL1 COL2 WHATEVER
11STUFF
22STUFF
33
44
SQL select * from tester2 where whatever not like '%STU%';
no rows selected
My
Why is this?? If I know that value X has no value, I certainly know that
value X is not like '%STU%' ?
From: Whittle Jerome Contr NCI [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Subject: RE: comparing null values
Date: Thu, 30 Jan 2003 13:15:33 -0600
Gary,
Null has
to use 'like' and 'not like'
on columns containing null values. (I am unable to find information
regarding this on MetaLink.)
For example:
SQL select * from tester2;
COL1 COL2 WHATEVER
11STUFF
22STUFF
33
44
SQL select * from tester2 where whatever
PROTECTED]
Subject: RE: comparing null values
Date: Thu, 30 Jan 2003 13:15:33 -0600
Gary,
Null has no value. It can't be like or not like anything. If you want to
see the null you'll need to add OR IS NULL to your Where clause.
Jerry Whittle
ASIFICS DBA
NCI Information Systems Inc.
[EMAIL PROTECTED
: RE: comparing null values
Date: Thu, 30 Jan 2003 13:15:33 -0600
Gary,
Null has no value. It can't be like or not like anything. If you want to
see the null you'll need to add OR IS NULL to your Where clause.
Jerry Whittle
ASIFICS DBA
NCI Information Systems Inc.
[EMAIL PROTECTED]
618-622-4145
Hi Gary,
I wonder why you didn't use :
select * from tester2 where whatever is null;
Null values is extremely empty.
Rgrds,
Sony
-Original Message-
From: Gary Jackson [SMTP:[EMAIL PROTECTED]]
Sent: Friday, January 31, 2003 12:42 AM
To: Multiple recipients of list ORACLE-L
Title: RE: NOT IN with NULL-values
Yes I had a null value in am91.
rgds
amar
-Original Message-
From: Kuijten, F. (Frank) [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 29, 2001 6:35 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: NOT IN with NULL-values
Amar
Title: RE: NOT IN with NULL-values
Sorry Frank,
I tried that without null. I cross checked and found results for not in similar to yours, as explained by other list members. null is not equal to another value, or null itself.
rgds
amar
-Original Message-
From: Kuijten, F. (Frank
Hello,
I'm running the SQL-statements below :
SQL create table fk_ldm1 (id number(10) not null);
Table created.
SQL insert into fk_ldm1 values(1);
1 row created.
SQL insert into fk_ldm1 values(2);
1 row created.
SQL insert into fk_ldm1 values(3);
1 row created.
SQL insert into fk_ldm1
Title: RE: NOT IN with NULL-values
I tried your example at my end. The both the NOT IN stmts do give me the result. NOT EXITS is functioning properly as there are records existing in sub-query. check the last stmt below for this. I see no bugs or issues. check this:
-select * from am90
Amar,
Thanks.
One question : Do you have a NULL value in the 'am91' table ?
Because that's where my problem is.
Without the NULL value, all queries are giving the expected results.
Greetings,
Frank
-Original Message-
Sent: maandag 29 oktober 2001 14:50
To: Multiple recipients
and return a
'true' value. Because the 'null' exists, it throws the whole query away -
as evidenced by #3 where you discard null values.
#2 does not work because you did not co-relate the two queries together.
Change it as suggested to:
select * from fk_ldm1
where not exists (select * from fk_ldm2 where
]
214.954.1781
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Kuijten, F.
(Frank)
Sent: Monday, October 29, 2001 8:35 AM
To: Multiple recipients of list ORACLE-L
Subject: RE: NOT IN with NULL-values
Amar,
Thanks.
One question : Do you have
hello!
our developers here are requesting that I put defaults (' ' for
chars/varchars, 0 for numbers, etc) in place instead of nulls in all
columns that would supposedly allow null values...
they are using visual c++ and they say that they cannot make visual c++
retreive null values...
i am very
of list ORACLE-L
hello!
our developers here are requesting that I put defaults (' ' for
chars/varchars, 0 for numbers, etc) in place instead of nulls in all
columns that would supposedly allow null values...
they are using visual c++ and they say that they cannot make visual c++
retreive null
If you use ODBC (CTransaction + CRecordset in MFC) there is no problem to
handle null values.
It isn't good idea to put 0 (zero) instead of null in number column.
JP
On Fri 19. October 2001 15:00, you wrote:
hello!
our developers here are requesting that I put defaults (' ' for
chars
Hi,
sorry for the strong language, but the statement that VC++ isn't able to
retrieve NULL values is plain bullshit.
| Regards, |
| Stefan Jahnke |
| BOV AG |
| @:D2 Vodafone, Abt.: FBOM |
| Tel.: 0211/533-4893
(' ' for
chars/varchars, 0 for numbers, etc) in place instead of nulls in all
columns that would supposedly allow null values...
they are using visual c++ and they say that they cannot make visual c++
retreive null values...
i am very hesitant in implementing this...
i have no knowledge whatsoever
recipients of list ORACLE-L
hello!
our developers here are requesting that I put defaults (' ' for
chars/varchars, 0 for numbers, etc) in place instead of nulls in all
columns that would supposedly allow null values...
they are using visual c++ and they say that they cannot make visual c
,
sorry for the strong language, but the statement that VC++ isn't able to
retrieve NULL values is plain bullshit.
| Regards, |
| Stefan Jahnke |
| BOV AG |
| @:D2 Vodafone, Abt.: FBOM |
| Tel.: 0211/533-4893
in all
columns that would supposedly allow null values...
they are using visual c++ and they say that they cannot make visual c++
retreive null values...
i am very hesitant in implementing this...
i have no knowledge whatsoever of visual c++ and don't know if this is
true...
i'd like to know
Hallo you DBA's:
How can I modify in this script to make it handle also null values. This script only
handles 0-values.
Hope anyone can help me with this.
vOWNERSHIP_NO:= rpad(to_char(nvl(recCursor.OWNERSHIP_NO,' 0')),2,' ');
Thanks in advance
Roland Sköldblom
--
Please see the official
29 matches
Mail list logo
