always alias the id on joins. Basically, it was a PITA, the aliases
weren't consistent, you had to remember if you'd used a join, you had to
change your output should you need to add a join.....
Yeah. We do ours by tablename, generally, now.
--Ben
Marlon Moyer wrote:
> Warning! : Silly question..
>
>
>
> I use identity fields in MSSql as my primary key. I'm getting ready to
> create a new database and was about to name my primary key field. In the
> past, I've based the name on the table name, ie on table orders, order_id.
> Sometimes that results in some long field names. So, does anyone see a
> downside to naming it a simple "id" or maybe "rowid" or "r_id" or something
> similar?
>
> Marlon
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
