Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Overloading words: How can we get Oracle to stop it?

RE: Overloading words: How can we get Oracle to stop it?

From: Jesse, Rich <Rich.Jesse_at_qg.com>
Date: Mon, 12 Jun 2006 12:26:36 -0500
Message-ID: <FB5D3CCFCECC2948B5DCF4CABDBE6697A51D91@QTEX1.qg.com>


This one's been my occasional thorn:

SELECT column_name, data_type, data_length, COUNT(*) FROM dba_tab_columns
WHERE column_name LIKE 'OBJ%NAME'
AND OWNER = 'SYS'
GROUP BY column_name, data_type, data_length ORDER BY 4 DESC; Rich


        From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Jared Still

	Sent: Monday, June 12, 2006 12:13 PM
	To: ganstadba_at_hotmail.com
	Cc: Oracle-L
	Subject: Re: Overloading words: How can we get Oracle to stop
it?                  
	While I understand your point, I don't think some
	of your examples are apropos.
	
	ie.  segment_owner, index_owner and table owner are not
synonymous.
	Each is the appropriate word in its own context.
	
	Jared 
	
	
	
	On 6/9/06, Michael McMullen <ganstadba_at_hotmail.com> wrote: 

		How about the use of different names for the same thing
in data dictionary
		views.
		ie segment_owner,table_owner,owner,index_owner,
timestamp,timestamp# etc.
		drives me crazy.
		


--
http://www.freelists.org/webpage/oracle-l
Received on Mon Jun 12 2006 - 12:26:36 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US