View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS

Tap the Share icon in Safari
Scroll the menu and tap Add to Home Screen.
Tap Add in the top-right corner.

To install this app on Android

Tap the 3-dot menu (⋮) in the top-right corner of the browser.
Tap Add to Home screen or Install app.
Confirm by tapping Install.

FMForums.com

Sign In

Email Address

Password

Remember me
Not recommended on shared computers

Forgot your password?

Or sign in with...
Sign Up

one table to rule them all

Followers

July 17, 20169 yr

I am starting a new DB and pondering the schema. In a past project I had various company types that required their own section but I had a parent table called company which would hold basically the company name. so:

company: company_name, id
- agency: [ separate table, agency details ]
- client: [ separate table, client details ]
- vendor: [ separate table, vendor details ]

I also did the same for contacts:

profile: first_name, last_name, id
- contact: [ separate table, contact details ]
- talent: [ separate table, talent details ]

The new project has similar requirements and I am wondering if I should normalize it further and merge company into profile. A major benefit is searching a single table and having it return all contact and company but I am wondering if this is straying form best practice or if you can foresee any downside.