By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,638 Members | 2,241 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,638 IT Pros & Developers. It's quick & easy.

Help! Complicated Relationships

P: n/a
Hello Everyone!

I'm trying to design a database for a library that stocks a range
of media. (see link)

http://homepage.ntlworld.com/james.m...te/library.gif

Each user can make many enquiries / reservations / loans
(if I can get enquiries right, I can do the rest). Every Enquiry
can be made on each item of stock, every item of stock is
a copy and every copy contains item info. Each item can be
of audio, book or score (musical score).

I would really appreciate any observations or advice where I'm
going right / where I'm going wrong. I would really appreciate
help with what queries I should make which will make it possible
eventually for a User to make an enquiry about any item of audio.

Thankyou for reading,

James

Nov 12 '05 #1
Share this Question
Share on Google+
15 Replies


P: n/a
Hi James

"James" <ja*********@ntlworld.com> schrieb im Newsbeitrag
news:XoQic.97$cy3.25@newsfe1-win...
Hello Everyone!

I'm trying to design a database for a library that stocks a range
of media. (see link)

http://homepage.ntlworld.com/james.m...te/library.gif


First of all, i would think a little about the naming-conventions
(tables and fields) tblUser looks much better than user-;)

Stay away from fieldnames like [E-Mail] or [Active Member?] and from
Spaces, "-" and ?. Makes life much easier in futuractions. (Queries,
sql)etc.

I miss the ID-Field (ID, PrimaryKey, Autonumber)

You have to work on your DBDesign: No Relation to the table Reservation?

Peter
Nov 12 '05 #2

P: n/a
When I look at your design I see that you have a function for "enquiry" and
no function for checking out books, so I'm thinking maybe an enquiry is when
you check out a book as opposed to inquiring about the existence of a book.
Is this correct?

You left out copynumber in audio and copynumber should be a PK if barcode is
not unique for each copy.

Robert

"James" <ja*********@ntlworld.com> wrote in message
news:XoQic.97$cy3.25@newsfe1-win...
Hello Everyone!

I'm trying to design a database for a library that stocks a range
of media. (see link)

http://homepage.ntlworld.com/james.m...te/library.gif

Each user can make many enquiries / reservations / loans
(if I can get enquiries right, I can do the rest). Every Enquiry
can be made on each item of stock, every item of stock is
a copy and every copy contains item info. Each item can be
of audio, book or score (musical score).

I would really appreciate any observations or advice where I'm
going right / where I'm going wrong. I would really appreciate
help with what queries I should make which will make it possible
eventually for a User to make an enquiry about any item of audio.

Thankyou for reading,

James

Nov 12 '05 #3

P: n/a
"Peter Steimann[MVP Access]" <PS************@Timesoft.ch> wrote in message
news:c6************@ID-93817.news.uni-berlin.de...
Hi James

"James" <ja*********@ntlworld.com> schrieb im Newsbeitrag
news:XoQic.97$cy3.25@newsfe1-win...
Hello Everyone!

I'm trying to design a database for a library that stocks a range
of media. (see link)

http://homepage.ntlworld.com/james.m...te/library.gif


First of all, i would think a little about the naming-conventions
(tables and fields) tblUser looks much better than user-;)

Peter, I think "user" is just fine for a table of users - if there will only
ever be one of them. Otherwise i'd go with "users".
"tblUser" is not good - there's no valid reason to use "tbl" "qry" prefixes
for database object names.

--
btw if this were a table of linux users do you think we could we call it
"lusers" <g>


Nov 12 '05 #4

P: n/a
Hello Robert,

Firstly, thankyou very much for replying to my cry for help!
I'm keen to emphasise that any comments/advice I receive
is very much appreciated.

Apologies for the vague post; I must admit, it isn't the
clearest post I've ever made!

The database I'm creating has (for my knowledge) developed
a lot since 4 o'clock today. Please check:
http://homepage.ntlworld.com/james.m...te/library.gif
as I've updated the image of the relationships in my database.

As far and Enquiries and Audio go, everything seems to work ok!! :oD
I'm thinking that the rest of the database will be easy once I've
worked out how I'm going to work with it in its present state.
This is why I left out any mention of other tables because I
wanted to concentrate on the enquiry-audio part of the database
(hope this makes sense!). The enquiries made by users are just
'points of interest' (It's pretty pointless but I had to include it), users
can make an enquiry on any item of stock (to find out whether its
on loan etc). Other actions the user can perform are:
2. reserving an item and 3. loaning or borrowing an item.
Of course, each user can have multiple enquiries, multiple reservations
and multiple loans.
The 'catalogue' as I'm sure you've guessed, is a way of controlling
each unique item by type: each item can either be a 'audio,' 'book,'
or 'Score.' I'm hoping to connect all these tables in the same fashion as
'audio' is connected now. I think this will work, what do you think ????

Naming conventions etc have been intentionally ignored because
I feel that the most important thing is to get the model working.

Ok, I hope that make things a little clearer. Let me know your
thoughts and I'll try to help you to help me!

Thanks Robert,
James

"Robert" <pr**********@yahoo.com> wrote in message
news:10*************@corp.supernews.com...
When I look at your design I see that you have a function for "enquiry" and no function for checking out books, so I'm thinking maybe an enquiry is when you check out a book as opposed to inquiring about the existence of a book. Is this correct?

You left out copynumber in audio and copynumber should be a PK if barcode is not unique for each copy.

Robert

"James" <ja*********@ntlworld.com> wrote in message
news:XoQic.97$cy3.25@newsfe1-win...
Hello Everyone!

I'm trying to design a database for a library that stocks a range
of media. (see link)

http://homepage.ntlworld.com/james.m...te/library.gif

Each user can make many enquiries / reservations / loans
(if I can get enquiries right, I can do the rest). Every Enquiry
can be made on each item of stock, every item of stock is
a copy and every copy contains item info. Each item can be
of audio, book or score (musical score).

I would really appreciate any observations or advice where I'm
going right / where I'm going wrong. I would really appreciate
help with what queries I should make which will make it possible
eventually for a User to make an enquiry about any item of audio.

Thankyou for reading,

James


Nov 12 '05 #5

P: n/a
Hi Peter,

Thanks for your reply.

I've just updated the image I captured of database relationships.
Please check again.

The naming conventions will be important, I did forget about
them earlier on nevertheless thankyou for reminding me! :o)

I wanted to concentrate on enquiries for audio as I think that
if I were to get this right, I could do the rest. As it stands,
everything appears to work! horray! However, I will probably
need more help so I've made a post lower down that makes
things clearer, sorry I can't type it all out again - my fingers
are beginning to ache!

James
"Peter Steimann[MVP Access]" <PS************@Timesoft.ch> wrote in message
news:c6************@ID-93817.news.uni-berlin.de...
Hi James

"James" <ja*********@ntlworld.com> schrieb im Newsbeitrag
news:XoQic.97$cy3.25@newsfe1-win...
Hello Everyone!

I'm trying to design a database for a library that stocks a range
of media. (see link)

http://homepage.ntlworld.com/james.m...te/library.gif


First of all, i would think a little about the naming-conventions
(tables and fields) tblUser looks much better than user-;)

Stay away from fieldnames like [E-Mail] or [Active Member?] and from
Spaces, "-" and ?. Makes life much easier in futuractions. (Queries,
sql)etc.

I miss the ID-Field (ID, PrimaryKey, Autonumber)

You have to work on your DBDesign: No Relation to the table Reservation?

Peter

Nov 12 '05 #6

P: n/a
Hi James,

I built a library database a while back....if your interested I can send you
a copy for review, it may be of some help. Let me know which version of
Access your using.
Cheers,

Dave

"James" <ja*********@ntlworld.com> wrote in message
news:XoQic.97$cy3.25@newsfe1-win...
Hello Everyone!

I'm trying to design a database for a library that stocks a range
of media. (see link)

http://homepage.ntlworld.com/james.m...te/library.gif

Each user can make many enquiries / reservations / loans
(if I can get enquiries right, I can do the rest). Every Enquiry
can be made on each item of stock, every item of stock is
a copy and every copy contains item info. Each item can be
of audio, book or score (musical score).

I would really appreciate any observations or advice where I'm
going right / where I'm going wrong. I would really appreciate
help with what queries I should make which will make it possible
eventually for a User to make an enquiry about any item of audio.

Thankyou for reading,

James

Nov 12 '05 #7

P: n/a
Hi Dave,

I'm using Access 2002 (think its part of Office XP).
If you could send it that would be excellent.
My Email is: ja*********@ntlworld.com

Many thanks,

James

"Dave Brydon" <db*****@ns.sympatico.ca> wrote in message
news:iP*********************@ursa-nb00s0.nbnet.nb.ca...
Hi James,

I built a library database a while back....if your interested I can send you a copy for review, it may be of some help. Let me know which version of
Access your using.
Cheers,

Dave

"James" <ja*********@ntlworld.com> wrote in message
news:XoQic.97$cy3.25@newsfe1-win...
Hello Everyone!

I'm trying to design a database for a library that stocks a range
of media. (see link)

http://homepage.ntlworld.com/james.m...te/library.gif

Each user can make many enquiries / reservations / loans
(if I can get enquiries right, I can do the rest). Every Enquiry
can be made on each item of stock, every item of stock is
a copy and every copy contains item info. Each item can be
of audio, book or score (musical score).

I would really appreciate any observations or advice where I'm
going right / where I'm going wrong. I would really appreciate
help with what queries I should make which will make it possible
eventually for a User to make an enquiry about any item of audio.

Thankyou for reading,

James


Nov 12 '05 #8

P: n/a
Okay. I see that you have a separate item Id and item barcode and item copy
number. I didn't see that at first. Each individual item in the library
can be identified with the item id or the combination of item barcode + copy
number. So the copy number in the Book table is not needed. It looked to
me at first like you had forgotten to put the copy number in the audio
table. Having 2 ways of identifying a book is redundant, but it might be
easier for the people who handle the books to work with a single number (if
they even look at the number).

I think you're on the right track. Go for it!

Robert
"James" <ja*********@ntlworld.com> wrote in message
news:e_Sic.146$cy3.82@newsfe1-win...
Hello Robert,

Firstly, thankyou very much for replying to my cry for help!
I'm keen to emphasise that any comments/advice I receive
is very much appreciated.

Apologies for the vague post; I must admit, it isn't the
clearest post I've ever made!

The database I'm creating has (for my knowledge) developed
a lot since 4 o'clock today. Please check:
http://homepage.ntlworld.com/james.m...te/library.gif
as I've updated the image of the relationships in my database.

As far and Enquiries and Audio go, everything seems to work ok!! :oD
I'm thinking that the rest of the database will be easy once I've
worked out how I'm going to work with it in its present state.
This is why I left out any mention of other tables because I
wanted to concentrate on the enquiry-audio part of the database
(hope this makes sense!). The enquiries made by users are just
'points of interest' (It's pretty pointless but I had to include it), users can make an enquiry on any item of stock (to find out whether its
on loan etc). Other actions the user can perform are:
2. reserving an item and 3. loaning or borrowing an item.
Of course, each user can have multiple enquiries, multiple reservations
and multiple loans.
The 'catalogue' as I'm sure you've guessed, is a way of controlling
each unique item by type: each item can either be a 'audio,' 'book,'
or 'Score.' I'm hoping to connect all these tables in the same fashion as
'audio' is connected now. I think this will work, what do you think ????

Naming conventions etc have been intentionally ignored because
I feel that the most important thing is to get the model working.

Ok, I hope that make things a little clearer. Let me know your
thoughts and I'll try to help you to help me!

Thanks Robert,
James

"Robert" <pr**********@yahoo.com> wrote in message
news:10*************@corp.supernews.com...
When I look at your design I see that you have a function for "enquiry" and
no function for checking out books, so I'm thinking maybe an enquiry is

when
you check out a book as opposed to inquiring about the existence of a

book.
Is this correct?

You left out copynumber in audio and copynumber should be a PK if

barcode is
not unique for each copy.

Robert

"James" <ja*********@ntlworld.com> wrote in message
news:XoQic.97$cy3.25@newsfe1-win...
Hello Everyone!

I'm trying to design a database for a library that stocks a range
of media. (see link)

http://homepage.ntlworld.com/james.m...te/library.gif

Each user can make many enquiries / reservations / loans
(if I can get enquiries right, I can do the rest). Every Enquiry
can be made on each item of stock, every item of stock is
a copy and every copy contains item info. Each item can be
of audio, book or score (musical score).

I would really appreciate any observations or advice where I'm
going right / where I'm going wrong. I would really appreciate
help with what queries I should make which will make it possible
eventually for a User to make an enquiry about any item of audio.

Thankyou for reading,

James



Nov 12 '05 #9

P: n/a
:oD Big Smiles!

Thanks for reminding me. I've made the changes (this
will also apply to table 'Score' which is yet another media type.

I've decided to migrate all attributes that all media types
have in common (i.e. a 'title' and a 'category') to the
catalogue. This should make things better. I've got until
Tuesday afternoon to complete this! agh!

Thanks for your help, and if you want, I can keep you
updated? (I might need the help :oP )
James

"Robert" <pr**********@yahoo.com> wrote in message
news:10*************@corp.supernews.com...
Okay. I see that you have a separate item Id and item barcode and item copy number. I didn't see that at first. Each individual item in the library
can be identified with the item id or the combination of item barcode + copy number. So the copy number in the Book table is not needed. It looked to
me at first like you had forgotten to put the copy number in the audio
table. Having 2 ways of identifying a book is redundant, but it might be
easier for the people who handle the books to work with a single number (if they even look at the number).

I think you're on the right track. Go for it!

Robert
"James" <ja*********@ntlworld.com> wrote in message
news:e_Sic.146$cy3.82@newsfe1-win...
Hello Robert,

Firstly, thankyou very much for replying to my cry for help!
I'm keen to emphasise that any comments/advice I receive
is very much appreciated.

Apologies for the vague post; I must admit, it isn't the
clearest post I've ever made!

The database I'm creating has (for my knowledge) developed
a lot since 4 o'clock today. Please check:
http://homepage.ntlworld.com/james.m...te/library.gif
as I've updated the image of the relationships in my database.

As far and Enquiries and Audio go, everything seems to work ok!! :oD
I'm thinking that the rest of the database will be easy once I've
worked out how I'm going to work with it in its present state.
This is why I left out any mention of other tables because I
wanted to concentrate on the enquiry-audio part of the database
(hope this makes sense!). The enquiries made by users are just
'points of interest' (It's pretty pointless but I had to include it),

users
can make an enquiry on any item of stock (to find out whether its
on loan etc). Other actions the user can perform are:
2. reserving an item and 3. loaning or borrowing an item.
Of course, each user can have multiple enquiries, multiple reservations
and multiple loans.
The 'catalogue' as I'm sure you've guessed, is a way of controlling
each unique item by type: each item can either be a 'audio,' 'book,'
or 'Score.' I'm hoping to connect all these tables in the same fashion as 'audio' is connected now. I think this will work, what do you think ????

Naming conventions etc have been intentionally ignored because
I feel that the most important thing is to get the model working.

Ok, I hope that make things a little clearer. Let me know your
thoughts and I'll try to help you to help me!

Thanks Robert,
James

"Robert" <pr**********@yahoo.com> wrote in message
news:10*************@corp.supernews.com...
When I look at your design I see that you have a function for
"enquiry" and
no function for checking out books, so I'm thinking maybe an enquiry
is when
you check out a book as opposed to inquiring about the existence of a

book.
Is this correct?

You left out copynumber in audio and copynumber should be a PK if

barcode
is
not unique for each copy.

Robert

"James" <ja*********@ntlworld.com> wrote in message
news:XoQic.97$cy3.25@newsfe1-win...
> Hello Everyone!
>
> I'm trying to design a database for a library that stocks a range
> of media. (see link)
>
> http://homepage.ntlworld.com/james.m...te/library.gif
>
> Each user can make many enquiries / reservations / loans
> (if I can get enquiries right, I can do the rest). Every Enquiry
> can be made on each item of stock, every item of stock is
> a copy and every copy contains item info. Each item can be
> of audio, book or score (musical score).
>
> I would really appreciate any observations or advice where I'm
> going right / where I'm going wrong. I would really appreciate
> help with what queries I should make which will make it possible
> eventually for a User to make an enquiry about any item of audio.
>
> Thankyou for reading,
>
> James
>
>
>



Nov 12 '05 #10

P: n/a
Hi John

"John Winterbottom" <as******@hotmail.com> schrieb im Newsbeitrag
news:c6************@ID-185006.news.uni-berlin.de...
"Peter Steimann[MVP Access]" <PS************@Timesoft.ch> wrote in message
news:c6************@ID-93817.news.uni-berlin.de...
Hi James

"James" <ja*********@ntlworld.com> schrieb im Newsbeitrag
news:XoQic.97$cy3.25@newsfe1-win...
Hello Everyone!

I'm trying to design a database for a library that stocks a range
of media. (see link)

http://homepage.ntlworld.com/james.m...te/library.gif
First of all, i would think a little about the naming-conventions
(tables and fields) tblUser looks much better than user-;)

Peter, I think "user" is just fine for a table of users - if there will only
ever be one of them. Otherwise i'd go with "users".
"tblUser" is not good - there's no valid reason to use "tbl" "qry" prefixes
for database object names.


You can name then however you wan't. Using naming-conventions makes life
easier. That's my experience.

-- btw if this were a table of linux users do you think we could we call it
"lusers" <g>
A user is a user...

Peter






Nov 12 '05 #11

P: n/a
"John Winterbottom" <as******@hotmail.com> wrote in message news:<c6************@ID-185006.news.uni-berlin.de>...
Peter, I think "user" is just fine for a table of users - if there will only
ever be one of them. Otherwise i'd go with "users".
"tblUser" is not good - there's no valid reason to use "tbl" "qry" prefixes
for database object names.


You shouldn't be allowed to be your own straight man :-). I could be
pedantic about this and quote some "lusers":

By common entity naming conventions, an entity name must be singular.
We therefore call the table where we store CDs "CD" and not "CDs." We
use this convention because each entity names an instance. For
example, the "San Francisco 49ers" is an instance of "Football Team,"
not "Football Teams."

MySQL and mSQL
Yarger, Reese and King
O'Reilly 1999

But I don't follow this convention myself even though I am a luser,
err.. instance of lusers, err.. listed in lusers. Although you are
correct about there being no pragmatic reasons for tbl and qry
prefixes (except maybe no duplicate names being allowed -- I like
associating qryData with tblData), it is easier for repliers and
others on the newsgroup to decipher what's going on when someone posts
their Code/SQL if they have such prefixes. I try not to get dogmatic
about naming conventions. Controls, OTOH, sometimes lend themselves
to easier solutions when a naming convention is used. For me, I think
clients really like to see what looks like organization so I'll keep
the tbl and qry prefixes.

James A. Fortune
Nov 12 '05 #12

P: n/a
"James Fortune" <ja******@oakland.edu> wrote in message
news:a6**************************@posting.google.c om...
"John Winterbottom" <as******@hotmail.com> wrote in message

news:<c6************@ID-185006.news.uni-berlin.de>...
Peter, I think "user" is just fine for a table of users - if there will only ever be one of them. Otherwise i'd go with "users".
"tblUser" is not good - there's no valid reason to use "tbl" "qry" prefixes for database object names.


You shouldn't be allowed to be your own straight man :-). I could be
pedantic about this and quote some "lusers":

By common entity naming conventions, an entity name must be singular.
We therefore call the table where we store CDs "CD" and not "CDs." We
use this convention because each entity names an instance. For
example, the "San Francisco 49ers" is an instance of "Football Team,"
not "Football Teams."

Entities are sets, or collections, of things, so it is logical to name them
in the plural.
Nov 12 '05 #13

P: n/a
You're welcome. Yes, keep me updated.

Robert

"James" <ja*********@ntlworld.com> wrote in message
news:VNVic.200$cy3.134@newsfe1-win...
:oD Big Smiles!

Thanks for reminding me. I've made the changes (this
will also apply to table 'Score' which is yet another media type.

I've decided to migrate all attributes that all media types
have in common (i.e. a 'title' and a 'category') to the
catalogue. This should make things better. I've got until
Tuesday afternoon to complete this! agh!

Thanks for your help, and if you want, I can keep you
updated? (I might need the help :oP )
James

"Robert" <pr**********@yahoo.com> wrote in message
news:10*************@corp.supernews.com...
Okay. I see that you have a separate item Id and item barcode and item

copy
number. I didn't see that at first. Each individual item in the library
can be identified with the item id or the combination of item barcode +

copy
number. So the copy number in the Book table is not needed. It looked to me at first like you had forgotten to put the copy number in the audio
table. Having 2 ways of identifying a book is redundant, but it might be easier for the people who handle the books to work with a single number

(if
they even look at the number).

I think you're on the right track. Go for it!

Robert
"James" <ja*********@ntlworld.com> wrote in message
news:e_Sic.146$cy3.82@newsfe1-win...
Hello Robert,

Firstly, thankyou very much for replying to my cry for help!
I'm keen to emphasise that any comments/advice I receive
is very much appreciated.

Apologies for the vague post; I must admit, it isn't the
clearest post I've ever made!

The database I'm creating has (for my knowledge) developed
a lot since 4 o'clock today. Please check:
http://homepage.ntlworld.com/james.m...te/library.gif
as I've updated the image of the relationships in my database.

As far and Enquiries and Audio go, everything seems to work ok!! :oD
I'm thinking that the rest of the database will be easy once I've
worked out how I'm going to work with it in its present state.
This is why I left out any mention of other tables because I
wanted to concentrate on the enquiry-audio part of the database
(hope this makes sense!). The enquiries made by users are just
'points of interest' (It's pretty pointless but I had to include it),

users
can make an enquiry on any item of stock (to find out whether its
on loan etc). Other actions the user can perform are:
2. reserving an item and 3. loaning or borrowing an item.
Of course, each user can have multiple enquiries, multiple reservations and multiple loans.
The 'catalogue' as I'm sure you've guessed, is a way of controlling
each unique item by type: each item can either be a 'audio,' 'book,'
or 'Score.' I'm hoping to connect all these tables in the same fashion

as 'audio' is connected now. I think this will work, what do you think ????
Naming conventions etc have been intentionally ignored because
I feel that the most important thing is to get the model working.

Ok, I hope that make things a little clearer. Let me know your
thoughts and I'll try to help you to help me!

Thanks Robert,
James

"Robert" <pr**********@yahoo.com> wrote in message
news:10*************@corp.supernews.com...
> When I look at your design I see that you have a function for "enquiry" and
> no function for checking out books, so I'm thinking maybe an enquiry is when
> you check out a book as opposed to inquiring about the existence of a book.
> Is this correct?
>
> You left out copynumber in audio and copynumber should be a PK if

barcode
is
> not unique for each copy.
>
> Robert
>
> "James" <ja*********@ntlworld.com> wrote in message
> news:XoQic.97$cy3.25@newsfe1-win...
> > Hello Everyone!
> >
> > I'm trying to design a database for a library that stocks a range
> > of media. (see link)
> >
> > http://homepage.ntlworld.com/james.m...te/library.gif
> >
> > Each user can make many enquiries / reservations / loans
> > (if I can get enquiries right, I can do the rest). Every Enquiry
> > can be made on each item of stock, every item of stock is
> > a copy and every copy contains item info. Each item can be
> > of audio, book or score (musical score).
> >
> > I would really appreciate any observations or advice where I'm
> > going right / where I'm going wrong. I would really appreciate
> > help with what queries I should make which will make it possible
> > eventually for a User to make an enquiry about any item of audio.
> >
> > Thankyou for reading,
> >
> > James
> >
> >
> >
>
>



Nov 12 '05 #14

P: n/a
rkc

"John Winterbottom" <as******@hotmail.com> wrote in message
news:c6************@ID-185006.news.uni-berlin.de...
"James Fortune" <ja******@oakland.edu> wrote in message
news:a6**************************@posting.google.c om...
"John Winterbottom" <as******@hotmail.com> wrote in message news:<c6************@ID-185006.news.uni-berlin.de>...
Peter, I think "user" is just fine for a table of users - if there
will only ever be one of them. Otherwise i'd go with "users".
"tblUser" is not good - there's no valid reason to use "tbl" "qry" prefixes for database object names.
You shouldn't be allowed to be your own straight man :-). I could be
pedantic about this and quote some "lusers":

By common entity naming conventions, an entity name must be singular.
We therefore call the table where we store CDs "CD" and not "CDs." We
use this convention because each entity names an instance. For
example, the "San Francisco 49ers" is an instance of "Football Team,"
not "Football Teams."

Entities are sets, or collections, of things, so it is logical to name

them in the plural.


A single row in a table is not an entities.

SELECT * FROM Employee WHERE EmployeeID = 1 doesn't
return a set of Employees.

If you Google this subject you can read for hours and still just have
to make up your own mind.


Nov 12 '05 #15

P: n/a
"rkc" <rk*@yabba.dabba.do.rochester.rr.bomb> wrote in message
news:Ac*******************@twister.nyroc.rr.com...


Entities are sets, or collections, of things, so it is logical to name them
in the plural.


A single row in a table is not an entities.

SELECT * FROM Employee WHERE EmployeeID = 1 doesn't
return a set of Employees.


no it doesn't , but

SELECT * FROM Employees WHERE Dept = 'Accounting'

probably will, (unless you work for a very small company like me).

If you Google this subject you can read for hours and still just have
to make up your own mind.


This is true. Use whatever works. I once read of a programmer who
endeavoured to make his code as obscure as possible - so he used a most
cryptic naming convention - I believe it was a misguided attempt to anhance
his job security. I would have thought it would have the opposite effect.
Nov 12 '05 #16

This discussion thread is closed

Replies have been disabled for this discussion.