Quoting is a necessary evil. Since I'm most familiar with postgres, I'll use it for case in point.
I don't use it, but Mixed case column names have the potential of being very handy. In order to use them, you must quote your column names, or postgres will default to lower case. There are, as previously stated a number of other reasons to use quotes. Okay, now that I've kicked the dead horse... How about including an option somewhere quoted_names=False to bypass the filter for debugging purposes??? -Joseph On Wed, 2007-02-14 at 12:22 -0500, Ed Leafe wrote: > On Feb 14, 2007, at 11:04 AM, Paul McNett wrote: > > > I think that the automatic quoting when spaces are present is nice, > > although not necessarily required if they have access to the > > hypothetical addQuotes() dBackend function. > > Hypothetical? You mean the 'encloseSpaces()' method? That's been > there for weeks. > > Also, we need to do this in the framework when we create udpate, > insert, delete, etc., statements. > > > No no no. Let's just drop it for now. > > Too late! ;-) > > I've committed the changes. I've been running it since yesterday > with MySQL and it hasn't shown any problems. I'm hoping that those > who are running Firebird, MS SQL and PostgreSQL will verify that it's > working for them, too. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
