On Thursday 15 February 2007 10:17, Paul McNett wrote: > johnf wrote: > > Thanks. One more request. Could we have it default to 'False'. I say > > this because it seems to me that we are encouraging bad DB design. It's > > one thing to say one has to work with a legacy system that requires > > quotes. It's another to say it's OK to create them. > > "Be tolerant when receiving; be strict when sending". This is part of > the RFC for sending email. I think it applies to life in general, as > well as design of things like Dabo. Let's be tolerant of the input by > default, so that people can get past their first baby steps using the > framework, but yet allow them to set it to a stricter setting themselves. -1 If some guy has "Eval", "eVal", "evaL" as field names and can't figure out he should have eval1, eval2, eval3 then he has a bigger problem than us providing a means to accommodate quoting. This is not us being intolerant we are providing a means to allow quoting.
I am willing to bet that the designers of the DB's that allow spaces, case for fields and tables regret it everyday - that includes Postgres. Ms SQL by default is not case sensitive. Instead of lowering ourself to the lowest denominator let us ask the user to raise his/her level to a NORMAL standard. If they have to be abnormal then they can turn on quoting. -- John Fabiani _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
