According to Date you should never use NULLs. This is because a NULL can
mean many different things. It can mean not known (e.g. I know he has an
age but I don't know what it is), It can be not applicable (e.g. in a
Party table of organizations and people, people would be of a certain sex
but an or
I think there is an echo in here :) It's probably me. I pass for the rest
of this thread.
> "Joost Kraaijeveld" <[EMAIL PROTECTED]> writes:
>> CREATE OR REPLACE VIEW even AS
>> SELECT DISTINCT abo_his.klantnummer,
>>> abo_his.artikelnummer, abo_his.code_retour,
>>> abo_klt.aantal_abonnementen, abo
I think I stated in my previous post but in order to make your view
consistent with your original query I think you should do:
CREATE OR REPLACE VIEW even AS
SELECT DISTINCT abo_his.klantnummer,
abo_his.artikelnummer, abo_his.code_retour,
abo_klt.aantal_abonnementen, abo_klt.afgewerkt
FROM abo
You haven't given the complete information but the following is just a guess.
It seems that abonnement is in both tables.
The view is stating
abo_his.abonnement = 238
I assume that your initial query was
WHERE abo_klt.abonnement = 238 and
AND abo_klt.afgewerkt > 2
My guess is that you are
>
>> based on the index values because 2004-12-02 is between the from and end
>> date. However, b and d would be excluded immediately because the the
>> from
>> date is greater than 2004-12-02 and would save the optimizer from even
>> reading the table for these index entries because the fromDate i
Try
SELECT *
FROM mytable
WHERE (identification_number,date_of_birth) IN
(SELECT identification_number
, date_of_birth
FROM mytable m2
GROUP BY identification_number,data_of_birth
HAVING COUNT(*) > 1
)
There are other ways
If you are experienced in Oracle, this might be confusing since Oracle
treats empty string and NULL as being the same.
> On Mon, 13 Oct 2003, Robert Partyka wrote:
>
>> why such condition:
>> foofield not like '%bar%'
>>
>> where foofield is varchar
>>
>> returns false (or rather even ignore row)
