|
|
Posted by AnrDaemon on 11/11/07 10:22
Greetings, Steve.
In reply to Your message dated Friday, November 9, 2007, 13:05:21,
>> As far as field names is a strings, You can use any given name, even in
>> Your
>> local encoding, and You can use spaces too.
> no, it's an alias for an object really. but, yes, you can name it whatever
> you wish. there is plenty of documentation in *every* db about avoiding such
> conventions, esp. reserved words as dbo names, like the plague.
>>> Then you don't need the quotes - which, BTW, are a MySQL extension to
>>> the SQL standard and won't work on any other RDBMS I'm familiar with.
>>
>> MS SQL Server use square brackets in the same way.
> so, you admit that mssql uses something DIFFERENT and PARTICULAR to alias?
> you realize that your code becomes TIED to that db until you rewrite every
> query to fit the NEXT db you want to use, don't you?
MS SQL uses different addressing schema anyway.
I always keep query sting templates in separate file, like localization
templates.
And I store them as constants to avoid modification at the time of script
execution.
So moving to different database is not a great issue. Smaller than
localization process.
--
Sincerely Yours, AnrDaemon <anrdaemon@freemail.ru>
Navigation:
[Reply to this message]
|