Path: dp-news.maxwell.syr.edu!spool.maxwell.syr.edu!drn.maxwell.syr.edu!news.maxwell.syr.edu!cyclone.bc.net!newsfeed2.telusplanet.net!newsfeed.telus.net!edtnps89.POSTED!53ab2750!not-for-mail From: Hans Forbrich Subject: Re: The reserved word "ACCESS" in a field list of a PL SQL Query Newsgroups: comp.databases.oracle.misc References: <719532c5.0409080702.7a5ec43c@posting.google.com> Lines: 27 User-Agent: KNode/0.7.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit Message-ID: Date: Thu, 09 Sep 2004 23:16:51 GMT NNTP-Posting-Host: 161.184.143.86 X-Trace: edtnps89 1094771811 161.184.143.86 (Thu, 09 Sep 2004 17:16:51 MDT) NNTP-Posting-Date: Thu, 09 Sep 2004 17:16:51 MDT Xref: dp-news.maxwell.syr.edu comp.databases.oracle.misc:112556 Turkbear wrote: > > Actually I was taught that a table has records which have fields and > that they only are called rows and columns because of the way they are > most often displayed, since they obviously are not arranged that way in > the database. > > > Tuples, anyone? ;-) My preference is for tuple/attribute for ER design, table/column for Relational implemetation & web page, record/field for forms & structure. Reason for tab/col - when I want to see a definition I look at DBA_TABLES and DBA_TAB_COLUMNS views provided by Oracle. (PErhaps you interrogate DBA_RECORDS?) WRT the post, I have seen the term 'field' mapped to 'form' rather too often. These days, when I hear a person grumble about things like field names in SELECT statements, I tend to think they've spent too much time with tools related to VB and Access - and then I think of the associated difficulties in explaining Oracle concepts to that person. However, I'll not quibble. /Hans