Odd behaviour if you use incorrect case for table name

I thought you might be interested in a bug that I traced to my having used the wrong case for the table name. This had me baffled for a while because the behaviour was not consistent, sometimes the error was duplicate key, other times wrong column count CORRECT BEHAVIOR =

Re: Obvious mistake in query?

Thanks! Phoebe. on 18/6/02 19:32, Ryan Fox at [EMAIL PROTECTED] wrote: > On Tue, 2002-06-18 at 14:11, Phoebe Bright wrote: >> I am trying to list items in t1 (alias new) that are not in project so I >> tried the query suggested on an earlier mail: >> >

Obvious mistake in query?

I am trying to list items in t1 (alias new) that are not in project so I tried the query suggested on an earlier mail: select new.projectdesc,project.projectname from t1 as new left join project on new.projectdesc=project.projectname where project.projectname=NULL | projectdesc | projectname |