I am not convinced that index on nullable field is a design flaw. This is not the
behavior in the major databases. To match and join two nulls, IS NULL should be
expected to be used instead of a.col1 = b.col2.
-Original Message-
From: Jan Steinman [mailto:[EMAIL PROTECTED]]
Sent: Thursd
Here is a correct one to solve your problem:
select b.city, b.name, b.numbeds, count(distinct a.numbeds) c from hospitals a,
hospitals b
where a.city = b.city
and a.numbeds>=b.numbeds
group by b.name, b.city, b.numbeds
having c=1;
-Original Message-
From: Myoung-Ah KANG [mailto:[EMAIL P
-Jianliang
-Original Message-
From: Heikki Tuuri [mailto:[EMAIL PROTECTED]]
Sent: 2002?10?8? 9:56
To: Jianliang Zhao; Mark Matthews
Cc: [EMAIL PROTECTED]
Subject: Re: transaction isolation level
Jianliang,
I tested that with two mysql clients, and it appeared to work ok. Check with
S
i Tuuri [mailto:[EMAIL PROTECTED]]
Sent: 2002?10?8? 0:22
To: Mark Matthews
Cc: [EMAIL PROTECTED]
Subject: Re: transaction isolation level
Hi!
- Original Message -
From: "Mark Matthews" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Tuesday, October 08, 2002
Thanks Jeremy. It turns out the JDBC SQL query tool(ViennaSQL) I am trying is causing
the problem. I couldn't reproduce the problem by writing a test case.
Thanks,
Jianliang
-Original Message-
From: Jeremy Zawodny [mailto:[EMAIL PROTECTED]]
Sent: 2002?10?7? 17:36
To: Jianliang Zh
Hi,
I am connecting to MySql 3.23(innodb) with mysql-connector-java-2.0.14-bin.jar. I set
the global transaction isolation level to READ COMMITTED. However, I still couldn't
see the committed changes through JDBC client. Does anyone know about this issue?
Thanks,
Jianliang
--
