Ed Leafe wrote: > On Feb 14, 2007, at 9:49 AM, Paul McNett wrote: > >>> No. If they're too clueless to use intelligent naming, they're too >>> clueless to realize that they need to quote things. >> It may be that they inherited the stupid naming, and need to work with >> it, at least temporarily. > > Sure, but this discussion isn't about someone who knows enough to > recognize that a name might pose a problem and properly escape it or > enclose it. It's about the framework taking preventative steps to > make sure that all naming works.
Sure, someone can just put the quotes in themselves, but not in a database-agnostic way. >>> What I'm saying is that *every* field, table name, etc., get >>> 'quoted' whether it has spaces or not. >> I don't like that, as that gets ugly to look at. > > Then you prefer something like the current system, where we check > for the existence of a space, and only add quotes if there is one, > leaving the rest untouched? 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. > Then tell you what: you provide me with a list of every possible > 'bad' name that will need quoting, and I'll write the code to check > every table and field name against that list, and only add quotes if > it's in that list. No no no. Let's just drop it for now. -- pkm ~ http://paulmcnett.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
