Prev: Question about recompiling a dll
Next: Grouping by Day for a Date Range
From: PENANCY on 25 Jun 2008 11:47
Hi!
I've read some article about naming convention and they all say don't
use number in the table name.
But I have a case that I can't figure out how to deal with it in a
proper name.
I have to import 2 flat files from FTP for OLAP use.
Both of these files contain similiar information,Customer data.

layout in file A is like
CUST_ID
NAME
GENDER
TEL
ADDRESS
and layout in file B is like
CUST_ID
FLAG_A
FLAG_B
......

I will join 2 tables in the next step.

Now I wonder what names are proper to these 2 tables.
I want to name them TB_CUST_1,TB_CUST_2
but these names are easily to be misunderstood by testing use.

is there any good name for them?

need your advice

thank you very much
From: --CELKO-- on 25 Jun 2008 17:15
>> I've read some article about naming convention and they all say don't use number in the table name. <<

The reason for that heuristic is that it is a sign of attribute
splitting -- that is, instead of having one table to model, say,
Personnel, you have split that set over smaller tables based on some
attribute, say, office number. Personnel_001, Personnel_002, etc.
will be joined back together and have to be validated constantly. It
is often a newbie error of confusing a file (mag tapes in particular)
with tables.

>> I have to import 2 flat files from FTP for OLAP use. Both of these files contain similar information, Customer data. <<

Look for what the table *is* by its nature. Your short descriptions
would lead me to guess at "CustomerDemographics" for A and
"CustomerSomething" for B, where something is what kind of data you
are getting -- purchases, survey results, etc. Oh, never use that
silly "tb-" affix on a table name (see ISO-11179); it tell us HOW the
data is stored, not what it is by its nature. Since we only have
tables in SQL, it is really redundant.

Do you have a copy of my SQL PROGRAMMING STYLE yet?
From: Sybaseguru on 25 Jun 2008 17:50
PENANCY(a)gmail.com wrote:

> Now I wonder what names are proper to these 2 tables.
> I want to name them TB_CUST_1,TB_CUST_2
> but these names are easily to be misunderstood by testing use.
>
> is there any good name for them?

How about 'CustomerDetails' and 'CustomerFlags' ?
From: PENANCY on 26 Jun 2008 10:23
Thanks for all your advice.

I'll tried to find these tables' nature and naming them in a proper
way.


On 6$B7n(B26$BF|(B, $B>e8a(B5$B;~(B50$BJ,(B, Sybaseguru <col...(a)usenet.cnntp.org> wrote:
> PENA...(a)gmail.com wrote:
> > Now I wonder what names are proper to these 2 tables.
> > I want to name them TB_CUST_1,TB_CUST_2
> > but these names are easily to be misunderstood by testing use.
>
> > is there any good name for them?
>
> How about 'CustomerDetails' and 'CustomerFlags' ?

From: Eric J. Holtman on 26 Jun 2008 11:28
--CELKO-- <jcelko212(a)earthlink.net> wrote in
news:0a51fc17-4f14-4775-a177-b8a4744e9509(a)z72g2000hsb.googlegroups.com:

> will be joined back together and have to be validated constantly. It
> is often a newbie error of confusing a file (mag tapes in particular)
> with tables.
>

As if a "newbie" even knows what a mag tape is.

 |  Next  |  Last
Pages: 1 2
Prev: Question about recompiling a dll
Next: Grouping by Day for a Date Range