![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I am constructing a regular expression to check the validity of an Oracle table name. What characters are valid? |
#3
| |||
| |||
|
|
What characters are valid? |
#4
| |||
| |||
|
|
On Sep 21, 6:42*am, Ramon F Herrera <ra... (AT) conexus (DOT) net> wrote: What characters are valid? Almost anything, if you use double quotes around the table name. You can even amaze your friends by creating tables with names that contain newlines and/or back spaces. -- Phil |
#5
| |||
| |||
|
|
On Sep 21, 6:42*am, Ramon F Herrera <ra... (AT) conexus (DOT) net> wrote: What characters are valid? Almost anything, if you use double quotes around the table name. You can even amaze your friends by creating tables with names that contain newlines and/or back spaces. -- Phil |
#6
| |||
| |||
|
|
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.] |
#7
| |||
| |||
|
|
On Sep 22, 12:30 am, Mark D Powell <Mark.Pow... (AT) eds (DOT) 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". |
#8
| |||
| |||
|
|
On Sep 22, 12:30*am, Mark D Powell <Mark.Pow... (AT) eds (DOT) 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 |
#9
| |||
| |||
|
|
On Sep 21, 6:29 pm, Phil Herring <phil_herr... (AT) yahoo (DOT) com.au> wrote: On Sep 22, 12:30 am, Mark D Powell <Mark.Pow... (AT) eds (DOT) 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 -- |
![]() |
| Thread Tools | |
| Display Modes | |
| |