John,
Sorry to hear about the kittens. 
As a developer that often has to maintain others' code, it's maddening to run into database table and column names that include spaces.
It's tempting to blame whoever designed the database schema, but when I think about that, I have a better target for my ire: the makers of databases that allow spaces in entity names to begin with.
What are they thinking? I have an old motto: Just because a thing can be done, doesn't mean it should be done. So the clever database designers could make spaces legal. Great. But at what cost to others down the road?
Say we need to name a data column. Is "Last Name" really any better a name than "LastName?" If so, I'd really like to understand why.
|
Regarding...
Paradox, .NET, and the Wicked Back-Tick
Using spaces within database column names may be "legal," but that doesn't mean it won't make your life harder. It's legal in Paradox tables and most database systems but you might want to avoid using spaces. Here's why - and one way to use spaces if you're using Paradox tables under .NET.
|
|