table naming convention about this case..

[PENANCY@gmail.com]

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,Cus tomer 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_CU ST_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

[--CELKO--]

Re: table naming convention about this case..

>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 "CustomerDemogr aphics" for A and
"CustomerSometh ing" 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?

[Sybaseguru]

Re: table naming convention about this case..

PENANCY@gmail.c om wrote:

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

How about 'CustomerDetail s' and 'CustomerFlags' ?

[PENANCY@gmail.com]

Re: table naming convention about this case..

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...@usenet. cnntp.orgwrote:

PENA...@gmail.c om wrote:

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

>

is there any good name for them?

>
How about 'CustomerDetail s' and 'CustomerFlags' ?

[Eric J. Holtman]

Re: table naming convention about this case..

--CELKO-- <jcelko212@eart hlink.netwrote in
news:0a51fc17-4f14-4775-a177-b8a4744e9509@z7 2g2000hsb.googl egroups.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.

[--CELKO--]

Re: table naming convention about this case..

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

They might not have seen them in their shops except in a back-up
device cassette, but they understand the sequential file access
concept from whatever their first procedural language was.

When I teach cursors, I map the SQL statements one-to-one against the
old IBM, DEC and Univac mag tape system commands.