I cannot understand the whole viewFoo and tblBar at all.

There is no distinction in the relational calculus between views and
tables, and they are properly treated as a single class of relation.

Which one is a base table, and which one is derived is a physical system
implementation, and should not be worried about by the programmer. If
there is a performance issue, then you adjust the database.

Putting tbl- and view- in front of the name is attaching an
implementation detail where it does not belong. If later you change what
was a view to become the base table, and what was the base table to
become a derived table, then you end up having to rejuggle all the
prefixes.

Yes, yes, I have perhaps read too much CJ Date, but I think he is spot
on with this topic.

--Sean

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Marlon Moyer
Sent: Tuesday, January 03, 2006 10:09 PM
To: [email protected]
Subject: Re: [CFCDev] Naming consistency

That one drives me crazy.  I could see if you want to prefix a view with
a 'v' if you really have to, but 'tbl'?.....arrrgh! 
Unfortunately, the VB programmer at my company wrote the coding
guidlines and that's the standard.


On 1/3/06, Patrick Branley <[EMAIL PROTECTED]> wrote:
> The only advantage of using the underscore for table columns is that 
> it gives you a clue that the data is raw data from a table an not a 
> formatted variable.
>
> eg. date_of_birth = {ts 2006-01-01 00:00:00} but dateOfBirth =
"01/01/2006"
>
> the one i find funny tho is where tables are prefixed with 'tbl' in 
> the database. Ive never really been confused if something was a view /

> sp or a table so i just dont see a need for this kind of naming
convention.
>
> Pat
>
>
>
>
> On 1/4/06, Hal Helms <[EMAIL PROTECTED]> wrote:
> > Ben,
> >
> > I've joked for years that database designers go to Langley, VA
> (headquarters
> > of the CIA) to learn how to name columns: that's the only 
> > explanation I
> can
> > come up with for some of the bizarre names we see. But I often alias

> > these in my SQL calls, as I feel it's important that the names be as

> > clear as possible. As for your naming conventions, the get/set model

> > is a very
> common
> > one. In Java, the convention is to use getX and setX while the .NET 
> > world uses GetX and SetX. The difference is that .NET encourages 
> > uppercasing
> when
> > the method is public.
> >
> > Hal
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On 
> > Behalf Of Ben Nadel
> > Sent: Tuesday, January 03, 2006 9:07 AM
> > To: [email protected]
> > Subject: [CFCDev] Naming consistency
> >
> >
> > So, I have some issues with the way things get named. Right now, 
> > when I create beans and entity objects, the propery names are 
> > get/set via mixed case methods (ex. GetUserName(), SetAge()). 
> > However, when I get a query
> via
> > a Gateway, the return properties (ie. column names) are all lower 
> > case
> with
> > underscores (ex. address_1, daytime_phone). Now it just seems weird 
> > to me that these two interfaces for similar sets of data would have 
> > different naming styles.
> >
> > So the question is two fold:
> >
> > 1. Are my naming conventions just way off (looking for opinion here,

> > not fact I know).
> > 2. Would it seem crazy to, in my SQL, rename the fields (ex. SELECT 
> > daytime_phone AS DayTimePhone FROM foo) so that the interfaces were 
> > more consistent?
> >
> > Thanks,
> > Ben
> >
> > ......................
> > Ben Nadel
> > Web Developer
> > Nylon Technology
> > 6 West 14th Street
> > New York, NY 10011
> > 212.691.1134
> > 212.691.3477 fax
> > www.nylontechnology.com
> >
> > Sanders: Lightspeed too slow?
> > Helmet: Yes we'll have to go right to ludacris speed.
> >
> >
> >
> >
> ----------------------------------------------------------
> > You are subscribed to cfcdev. To unsubscribe, send an email to 
> > [email protected] with the words 'unsubscribe cfcdev' as the 
> > subject of
> the
> > email.
> >
> > CFCDev is run by CFCZone ( www.cfczone.org) and supported by 
> > CFXHosting (www.cfxhosting.com).
> >
> > An archive of the CFCDev list is available at 
> > www.mail-archive.com/[email protected]
> >
> >
> >
> >
> >
> >
> ----------------------------------------------------------
> > You are subscribed to cfcdev. To unsubscribe, send an email to
> [email protected] with the words 'unsubscribe cfcdev' as the subject 
> of the email.
> >
> > CFCDev is run by CFCZone (www.cfczone.org) and supported by 
> > CFXHosting (
> www.cfxhosting.com).
> >
> > An archive of the CFCDev list is available at
> www.mail-archive.com/[email protected]
> >
> >
> >
>
> ----------------------------------------------------------
> You are subscribed to cfcdev. To unsubscribe, send an email to 
> [email protected] with the words 'unsubscribe cfcdev' as the subject 
> of the email.
>
> CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting

> (www.cfxhosting.com).
>
> An archive of the CFCDev list is available at 
> www.mail-archive.com/[email protected]


--
Marlon

A spaceman came travelling on his ship from afar, 'twas light years of
time since his mission did start, And over a village he halted his
craft, And it hung in the sky like a star, just like a star...
--Chris De Burgh, A Spaceman Came Travelling


----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of
the email.

CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).

An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]






----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to 
[email protected] with the words 'unsubscribe cfcdev' as the subject of the 
email.

CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting 
(www.cfxhosting.com).

An archive of the CFCDev list is available at 
www.mail-archive.com/[email protected]


Reply via email to