| ora-00972 (identifier too long) vs. design [message #409093] |
Fri, 19 June 2009 06:02  |
mdoh
Messages: 2
Registered: June 2009
|
Junior Member |
|
|
Hello,
I'm pretty new to Oracle and I'm in the process of porting a DB schema from Postgres to Oracle 10g. I hit the famous ora-00972 now.
Our Postgres DB reflects the names of our application's data models but these names break the 30 char limit of Oracle. The names often are combined names with prefixes separated by an underscore, e.g. "mymodule_specialperson_bankaccount".
If I now enforce abbreviations of the names to meet Oracle's needs I totally give up this nice structure. We've got a couple of tables (around 100 altogether) where we were able to group them logically by this naming scheme.
Could anybody advice me if there is an "Oracle way" to divide/design these things?
Kind regards
mdo
[Updated on: Fri, 19 June 2009 06:13] Report message to a moderator |
|
|
|
|
|
| Re: ora-00972 (identifier too long) vs. design [message #409117 is a reply to message #409093] |
Fri, 19 June 2009 08:28  |
JRowbottom
Messages: 5933
Registered: June 2006
Location: Sunny North Yorkshire, ho...
|
Senior Member |
|
|
I've personally never seen the point of including system or table identifiers in a column name.
A column is a part of a table - that's all. The column name should describe the data that the column holds in the context of that table.
|
|
|
|
|
|
|
|
|
|
| Re: ora-00972 (identifier too long) vs. design [message #409165 is a reply to message #409142] |
Fri, 19 June 2009 15:27 |
 |
Littlefoot
Messages: 21823
Registered: June 2005
Location: Croatia, Europe
|
Senior Member
Account Moderator |
|
|
|
As far as I can tell, the answer doesn't change much - length is limited to 30 characters and that's it. Unfortunately, it means that you'll have a lot to do while translating table (and perhaps column) names to fit Oracle's naming conventions.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
