Re: What character are valid in the name of a table?
From: Shakespeare <whatsin_at_xs4all.nl>
Date: Tue, 22 Sep 2009 15:55:09 +0200
Message-ID: <4ab8d735$0$83235$e4fe514c_at_news.xs4all.nl>
Mark D Powell schreef:
> On Sep 21, 6:29 pm, Phil Herring <phil_herr..._at_yahoo.com.au> wrote:
>
> My answer was directed to the serious adverse consequences of not
> sticking to the standard non-quoted identifiers as detailed in the SQL
> manual, which you had said were technically valid. It is a very bad
> idea.
>
> IMHO -- Mark D Powell --
Date: Tue, 22 Sep 2009 15:55:09 +0200
Message-ID: <4ab8d735$0$83235$e4fe514c_at_news.xs4all.nl>
Mark D Powell schreef:
> On Sep 21, 6:29 pm, Phil Herring <phil_herr..._at_yahoo.com.au> wrote:
>> On Sep 22, 12:30 am, Mark D Powell <Mark.Pow..._at_eds.com> wrote: >> >>> You will also create a nightmare for maintenance. I strongly suggest >>> sticking to the use of A - Z, 0 - 9, and underscore to all database >>> object names. [&c.] >> Sure. And Oracle recommend sticking to ASCII. And I get pretty annoyed >> with people who use mixed case where it isn't appropriate. I've even >> inherited code (I think it originated in a SQL Server system) that had >> spaces in table and column names. Irritating. >> >> However, if the question is "What characters are valid?", the answer >> is still: "anything you can type with the keyboard in front of you". >> >> -- Phil
>
> My answer was directed to the serious adverse consequences of not
> sticking to the standard non-quoted identifiers as detailed in the SQL
> manual, which you had said were technically valid. It is a very bad
> idea.
>
> IMHO -- Mark D Powell --
alt-003 may have very surprising effects for some tools!
Shakespeare Received on Tue Sep 22 2009 - 08:55:09 CDT