Bhaskar,

Wisely you chose to take 30 char limit in your stride but I'm sure the "name
translation algorithm" suggestion was intended as a joke and so was "doing
away with DDL". 

Don't make things overly complicated. Have good naming conventions and
shorten the name wherever wise. Name translation is going to make more
problems than name abbreviation. Can you give a brief of what problems you
anticipate by shortening the names?

Agreed, that 30 chars is a bit too mean, but thats the way it is. So better
learn to live with it rather than doing fancy things with a DB. 

Regards
Naveen
> -----Original Message-----
> From: Bhaskar Viswanathan [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 13, 2003 12:59 PM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: db file sequential read [WAS:wait event puzzler]
> 
> 
> 
> Hi,
> 
> Thanks to all for you responses.
> 
> To sum up the suggestions:
> 
> 1)    You can modify col$.NAME to varchar2(60) and try......  
> 2)    I do agree with you. But some times we may need go beyond the
> scopes.
>       For testing purpose we can do these kind of R&D's.(alterning the
> col.Cname size)
>       Nothing wrong in this.
> 3)    That is a Very Good Idea...
>       We will do away with DDL Stmts will start writing directly into
> the Data Dictionary ...
> 4)    Oracle does not support column names that are longer than 30
> characters.  
>       This is a hard standard and can not be changed.
> 5)    Ur not supposed to Update Data Dictionaly Tables Directly ... 
>       Oracle has A Limit of 30 Chrs and is Hardcoded.. So ReName your
> Columns within 30 Chrs... 
> 6)    Updating a data dictionary is simply not done. Remember, we're 
>       the DBA (you will be assimilated) and not fun loving students
> who can play with their alma mater's equipment. 
>       Updating the data dictionary directly would cause the database
> to lose support from 
>       Oracle Corp. and the perpetrator would be liable.
> 7)    telling him to do a Update on COL$... He Ends up Doing that in
> his Production Database.. 
>       And he is going to be in a HOT soup....
> 8)    Write a compress / decompress algorithm that will take your
> 200-character table names from 
>       the application and pass them to the database as <= 30
> characters; then uncompress them from 
>       the database back to the application.
> 9)    references to DB naming conventions.
> 
> I would want to go with the majority. "Do not Do it!!!!!!".
> 
> But then, the problem is like, I cannot afford to shorten 
> names as there
> are a lot of other problems which crops up.
> Though right now, thatz what we do and which is what I am 
> attempting to
> avoid.
> Ofcourse, the suggestion to have an algo. translate the names 
> is a good
> one, which is thought of and is the current
> Decision. 
> 
> Whew!, if oralce supports more than 30 characters for column 
> names, life
> would be easier.
> 
> Can somebody explain in brief, why this is being restricted to 30
> characters?
> 
> And once again, thanks a lot!
> 
> Baski
> 
> -----Original Message-----
> Sent: Thursday, June 12, 2003 7:10 PM
> To: Multiple recipients of list ORACLE-L
> 
> 
> Modifying  data dictionary tables is definitely not a  good 
> idea and I 
> am sure Oracle will not support this.
> 
> CP
> 
> 
> [EMAIL PROTECTED] wrote:
> 
> >Dear Bhaskar,
> >
> >You can modify col$.NAME to varchar2(60) and try.
> >
> >If this fails, I'll give a procedure you can use that to 
> change it to 
> >whatever size you want.
> >
> >Senthil Kumar
> >Sr Oracle DBA
> >Summitworks Technologies Pvt Ltd
> >
> >-----Original Message-----
> >Bhaskar Viswanathan
> >Sent: Thursday, June 12, 2003 4:00 PM
> >To: Multiple recipients of list ORACLE-L
> >
> >
> >
> >hi,
> >
> >We use Oracle 8 DB.
> >
> >I am not a Oracle technical guy. So lemme try explaining the problem.
> >
> >We need to create tables with columns, whose names(column-names) are 
> >more than 30 characters long. This is being restricted because, all 
> >columns of all tables have entries in a table called 'col'.
> >Thit table is defined as:
> >
> >SQL> desc col
> > Name                                      Null?    Type
> > ----------------------------------------- --------
> >----------------------------
> > TNAME                                     NOT NULL VARCHAR2(30)
> > COLNO                                     NOT NULL NUMBER
> > CNAME                                     NOT NULL VARCHAR2(30)
> > COLTYPE                                            VARCHAR2(106)
> > WIDTH                                     NOT NULL NUMBER
> > SCALE                                              NUMBER
> > PRECISION                                          NUMBER
> > NULLS                                              VARCHAR2(19)
> > DEFAULTVAL                                         LONG
> > CHARACTER_SET_NAME                                 VARCHAR2(44)
> >SQL>
> >
> >since CNAME is defined as VARCHAR2(30), we are forced to 
> retrict column
> 
> >names to a max of 30 characters long.
> >
> >For eg. create table T1(xxxxxxxxxxxxxxxxxxxxxxxxxxxxx31 
> varchar2(50)); 
> >The above statement will be rejected with the error:
> >                 *
> >ERROR at line 1:
> >ORA-00972: identifier is too long
> >
> >However, the statement "create table 
> T1(xxxxxxxxxxxxxxxxxxxxxxxxxxxx30 
> >varchar2(50))" Succeeds in creating the table;
> >
> >I guess this table col is created by the system itself. how can we 
> >change this size So that the 30 character restriction in 
> column names 
> >can be avoided???
> >
> >baski
> >
> >**************************Disclaimer*************************
> **********
> >*
> >
> >Information contained in this E-MAIL being proprietary to 
> Wipro Limited
> 
> >is 'privileged' and 'confidential' and intended for use only by the 
> >individual  or entity to which it is addressed. You are 
> notified that 
> >any use, copying or dissemination of the information 
> contained in the 
> >E-MAIL in any manner whatsoever is strictly prohibited.
> >
> >*************************************************************
> **********
> >****
> >--
> >Please see the official ORACLE-L FAQ: http://www.orafaq.net
> >--
> >Author: Bhaskar Viswanathan
> >  INET: [EMAIL PROTECTED]
> >
> >Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
> >San Diego, California        -- Mailing list and web hosting services
> >---------------------------------------------------------------------
> >To REMOVE yourself from this mailing list, send an E-Mail message
> >to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') 
> and in the
> 
> >message BODY, include a line containing: UNSUB ORACLE-L (or 
> the name of
> 
> >mailing list you want to be removed from).  You may also 
> send the HELP 
> >command for other information (like subscribing).
> >
> >  
> >
> 
> -- 
> Your favorite stores, helpful shopping tools and great gift ideas. 
> Experience the convenience of buying online with [EMAIL PROTECTED] 
> http://shopnow.netscape.com/
> 
> 
> -- 
> Please see the official ORACLE-L FAQ: http://www.orafaq.net
> -- 
> Author: CP
>   INET: [EMAIL PROTECTED]
> 
> Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
> San Diego, California        -- Mailing list and web hosting services
> ---------------------------------------------------------------------
> To REMOVE yourself from this mailing list, send an E-Mail message
> to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') 
> and in the
> message BODY, include a line containing: UNSUB ORACLE-L (or 
> the name of
> mailing list you want to be removed from).  You may also send the HELP
> command for other information (like subscribing).
> 
> **************************Disclaimer**************************
> **********
> 
> Information contained in this E-MAIL being proprietary to 
> Wipro Limited is 
> 'privileged' and 'confidential' and intended for use only by 
> the individual
>  or entity to which it is addressed. You are notified that 
> any use, copying 
> or dissemination of the information contained in the E-MAIL 
> in any manner 
> whatsoever is strictly prohibited.
> 
> **************************************************************
> *************
> -- 
> Please see the official ORACLE-L FAQ: http://www.orafaq.net
> -- 
> Author: Bhaskar Viswanathan
>   INET: [EMAIL PROTECTED]
> 
> Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
> San Diego, California        -- Mailing list and web hosting services
> ---------------------------------------------------------------------
> To REMOVE yourself from this mailing list, send an E-Mail message
> to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
> the message BODY, include a line containing: UNSUB ORACLE-L
> (or the name of mailing list you want to be removed from).  You may
> also send the HELP command for other information (like subscribing).
> 


DISCLAIMER:
This message (including attachment if any) is confidential and may be privileged. 
Before opening attachments please check them for viruses and defects. MindTree 
Consulting Private Limited (MindTree) will not be responsible for any viruses or 
defects or any forwarded attachments emanating either from within MindTree or outside. 
If you have received this message by mistake please notify the sender by return  
e-mail and delete this message from your system. Any unauthorized use or dissemination 
of this message in whole or in part is strictly prohibited.  Please note that e-mails 
are susceptible to change and MindTree shall not be liable for any improper, untimely 
or incomplete transmission.
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Naveen Nahata
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to