Well..well...So we have people hating case sensitivity...
I would like to add something here...
cASE SEnSitiVITY is not good for the whole of the database. I do agree that it saves '40%' time... but should be used only for columns that actually require it. A closer look at the system - I mean in the design level - would probably tell you more. If the situation says 'CaseSensitive' then the particular coulmn should be and if it says 'iTsOk' then it's ok.
More... if your product is going to be developed across different languages...it's lot more than just advisable to have case insensitive data base. People who are working in case insensitive environment would naturally think "select * from contact" would eventually result in "SELECT * FROM CONTACT". Not always they sense that the statement inside the quotes go into a different environment where case matters a lot. While flowing through the code...It's not possible for them to think all these...they have enough things to worry about.
AS for them... they just poured the midnight's oil helping there code find the DB server at '192.168.0.21' and just today morning they found that they have mistakenly typed '192.168.0.2l'...( btw... why did you hard code the server's IP address on the first place!??!!)
The above just put one more thing in picture. Many of the IDEs use CourierNew where 'l' and '1' look all the same. If I have a column say 'Col1' (btw... don't tell me that u really named a column as 'Col1'!) one might think it as 'Co11' or 'Coll'...that gives enough confusion. So - for those from the case sensitive camp - can you agree 'COL1' would be better.
And finally...for those who "Just wonder why modern languages are case sensitive!"...I would like to tell my personal opinion...I understand the program much. More, it makes way for some meaningful variable names and things like that...though forcibly.
if( strString.isEmpty() )
//it is empty.
// it is not empty.
does it not look like a sentence rather than scaring people with all upper case instructions...people those have seen the good old days of BASIC might agree with me.
but still some of the new programmers think using a BP is quite labour intensive...as for them..they'll know the real picture in the near future.
I am wedded with case sensitive programing...I love that...No question of a divorce.
Different Programing languages are for different purposes...and based on that, they are case sensitive or otherwise. But databases are common to all. They should easily integrate into any front end code. Hence I strongly feel that Case Insensitive Database is much more accesible.
Edited by - rajbow on 10/31/2001 12:32:40 AM
Edited by - rajbow on 10/31/2001 12:33:41 AM
It's the music that matters for a soulful experience... not the instrument.