RE: Enlightenment via avoiding the T-word

[David Hunter <david.hunter@mobileq.com>]

[Sorry for the HTML in the previous post.  Hopefully this one will be
better.]

Yes, we do alias in our SQL queries.  In fact, we alias everything; it helps
to break that tie between business layers and data layers.  And yes, there
may be cases where I need to get the "name" column from the "customer"
table, and the "name" column from the "person" table, all within the same
query, and alias them "CustomerName" and "PersonName" respectively.  But
this is only for the benefit of processing the data more easily.  There will
be other processing that we need to do which doesn't need to do this.  There
is no problem, from the database, telling which "name" is which, because
each is in it's own table.

To me, and this analogy is in danger of getting less and less like the
problem at hand, performing this type of query, and getting back a result
set, would be like taking one XML document (or a couple of XML documents),
and transforming it via XSLT to another XML document - some
elements/attributes/etc. may get renamed, but that doesn't mean that the
initial XML document is structured in a bad way - it just solved a different
problem than the new one does.

-----Original Message-----
From: Bullard, Claude L (Len) [mailto:clbullar@ingr.com]
Sent: Tuesday, August 28, 2001 3:11 PM
To: David Hunter; xml-dev@lists.xml.org
Subject: RE: Enlightenment via avoiding the T-word


You don't alias in SQL queries? You don't use associative names in queries?
Len 
http://www.mp3.com/LenBullard

Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h

-----Original Message-----
From: David Hunter [mailto:david.hunter@mobileq.com]

  I myself, and probably others on the list, would have said the opposite is
good practice - don't include the name of the parent element in the name of
the child element.  (I do the same when designing databases, not that I do
that too often.  I never include the table name in a column name.)