Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6868257
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T03:24:42+00:00 2026-05-27T03:24:42+00:00

I have table Widgets and table Persons both of them contains Identity column (

  • 0

I have table Widgets and table Persons

both of them contains Identity column ( seed)

what is the recommended naming convention for the identity column ?

is it “id” ( for both tables ) :

Widgets.Id
Persons.Id

or

Widgets.WidgetId
Persons.PersonId

Is there advantages / disadvantages in the former compare to the latter ?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-27T03:24:43+00:00Added an answer on May 27, 2026 at 3:24 am

    This is one case where I’d go for redundancy and have Thing.ThingID
    Otherwise you have to alias it everywhere when you JOIN

    Note: this was already done to death and beyond on programmers.se:
    Why is naming a table’s Primary Key column “Id” considered bad practice?

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Say you have WIDGETS table: WidgetID int ColorID int (Lookup values: Red, Blue, Green,
I currently have a Table [org.eclipse.swt.widgets.Table] with several TableColumns; however, due to UI space
In PostgreSQL 8.3, let's say I have a table called widgets with the following:
I have two tables. One (Widgets) has a list of widgets (ID, widget_name, color,
I have a 3 column table (name, author, and date). When the page loads,
I have two tables. Widgets, which has information about each widget (Color, size, etc);
I'm making a website to sell widgets. I have a table for widgets, each
I have a table in a database that contains a variety of paths to
I have a grid view that lists contents of a table, table has column
I have a fairly simple table called widgets. Each row holds an id, a

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.