Re: Help! Complicated Relationships
"rkc" <rkc@yabba.dabb a.do.rochester. rr.bomb> wrote in message
news:Acfjc.1749 2$X14.16111@twi ster.nyroc.rr.c om...[color=blue][color=green]
> >
> >
> > Entities are sets, or collections, of things, so it is logical to name[/color]
> them[color=green]
> > in the plural.[/color]
>
> A single row in a table is not an entities.
>
> SELECT * FROM Employee WHERE EmployeeID = 1 doesn't
> return a set of Employees.[/color]
no it doesn't , but
SELECT * FROM Employees WHERE Dept = 'Accounting'
probably will, (unless you work for a very small company like me).
[color=blue]
> If you Google this subject you can read for hours and still just have
> to make up your own mind.
>
>[/color]
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.
"rkc" <rkc@yabba.dabb a.do.rochester. rr.bomb> wrote in message
news:Acfjc.1749 2$X14.16111@twi ster.nyroc.rr.c om...[color=blue][color=green]
> >
> >
> > Entities are sets, or collections, of things, so it is logical to name[/color]
> them[color=green]
> > in the plural.[/color]
>
> A single row in a table is not an entities.
>
> SELECT * FROM Employee WHERE EmployeeID = 1 doesn't
> return a set of Employees.[/color]
no it doesn't , but
SELECT * FROM Employees WHERE Dept = 'Accounting'
probably will, (unless you work for a very small company like me).
[color=blue]
> If you Google this subject you can read for hours and still just have
> to make up your own mind.
>
>[/color]
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.
Comment