Is it a good or bad idea to include numbers in SQL table names?

Question

Clearly, you can use numeric characters in SQL table names and use them until they are at the beginning. (One of the side effects is discussed here: SQLite problem with table names using numbers? ) The database I'm targeting is Oracle 10g / 11g.

I am developing a database of reports where the names of some of the objects are clearly best done by describing reports that are named after numbers ("part 45", "102S", "401"). This is simply the language of the business domain: these reports are usually not called by any other name. The entities I model are best named in this way.

My question is: will I have difficulty with maintenance or programmability if I put numbers in the table name? I always worry about supporting software around the database: drivers, ETL code that you might not like with an unequal vanilla name. But is there any real benefit in legibility in this area of ​​business, so am I just squeamish?

My question is simply this: are there any "gotchas" or corner cases that would exclude the table name, like PART_45_AUDIT?

Answer 1

PART_45_AUDIT - , ( ), , . , , , . , , , .

CREATE TABLE "102S" (
  col1 number
);

SELECT *
  FROM "102S"