-
From: howard gramer [mailto:[EMAIL PROTECTED]]
Sent: Monday, 22 October 2001 11:40 AM
To: [EMAIL PROTECTED]
Subject: Re: Field Naming Standards
ummm, is there any thing wrong with using the Naming Convention devloped by
Stan Leszynski and Greg Reddick, authors of Access 97 books?
Their
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Yiu Wing" <[EMAIL PROTECTED]>
Sent: Sunday, October 21, 2001 9:52 PM
Subject: Re: Re: Field Naming Standards
> Your message cannot be posted because it appears to be either spam or
> simply off topic
On Sun, Oct 21, 2001 at 11:40:05PM -0400, jim barchuk wrote:
> The point of all this is to make it it easier to read -later-. A
> tbl_ is clearly a table and a b_ is clearly a boolean without having
> to think about it or 'remember' or look it up elsewhere. Such as 'I
> need to test this variable
H Jeremy!
> > tblNews
> > intpkNewsID
> > intfkUsersID
> > datPosted
> > varSubject
> > txtContent
> > blnBoolean
>
> Wow, that's rather cluttered. I'd rather use a readable standard.
> Won't it be a bit strange when you run SHOW TABLES and you get a bunch
> things back all that being with "tbl"
On Sun, Oct 21, 2001 at 09:40:16PM -0400, howard gramer wrote:
>
> ummm, is there any thing wrong with using the Naming Convention
> devloped by Stan Leszynski and Greg Reddick, authors of Access 97
> books?
>
> Their conventions would creat this:
>
> tblNews
> intpkNewsID
> intfkUsersID
> datPo
= primary key
fk = foreign key
The capitals are my preference.
- Original Message -
From: "Mike E" <[EMAIL PROTECTED]>
To: "ryc" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, October 20, 2001 3:36 PM
Subject: Re: Field Naming Standards
to be as close to natural
language as possible, for the same reason, and this helps.
In the end consistency is essential, much of the rest is personal
preference.
Peter
> -Original Message-
> From: ryc [mailto:[EMAIL PROTECTED]]
> Sent: 20 October 2001 19:48
> To: Mike
On 20-Oct-2001 Mike E wrote:
> That seems to follow how I've been doing it as well.
>
> For example, consider this database set up:
>
> Table: news
> Fields:
> newsid int(10)
> userid int(10)
> dateposted datetime
> subject varchar(255)
> content text
>
> Table: users
> Fields:
> userid int(10
That seems to follow how I've been doing it as well.
For example, consider this database set up:
Table: news
Fields:
newsid int(10)
userid int(10)
dateposted datetime
subject varchar(255)
content text
Table: users
Fields:
userid int(10)
name varchar(60)
and on and on. I'd love to hear from som
I am not aware of any document that describes naming conventions, but
through my use of databases and design I have found a scheme that works for
me. I follow these rules:
1. The autoincrement field (or unique id) for a table is named "tablename"
++ "id". So if the table is "books" the unique ide
Howdy,
I've been developing in MySQL for some time now, but as I go along I've
noticed that my naming conventions have changed dramatically, and I was
wondering if there is like a set of guidelines or something I could take
a look at. A set of standards, if you will, for naming conventions of
11 matches
Mail list logo
