Implementing bussiness logic with a large number of business rules and processes

We are currently working on a project that heavily relies on a database.
Among many tables the main focus is on table “data” which is linked to another table “data_type” as many-to-one, which is then linked to table “data_operation” as one-to-many.

Implementing bussiness logic with a large number of business rules and processes

We are currently working on a project that heavily relies on a database.
Among many tables the main focus is on table “data” which is linked to another table “data_type” as many-to-one, which is then linked to table “data_operation” as one-to-many.

How to represent one special related record

I have two tables, project and photo. photo has ID,projectID,path : each project has multiple photos.

How to represent one special related record

I have two tables, project and photo. photo has ID,projectID,path : each project has multiple photos.

How to represent one special related record

I have two tables, project and photo. photo has ID,projectID,path : each project has multiple photos.

How to represent one special related record

I have two tables, project and photo. photo has ID,projectID,path : each project has multiple photos.

How to represent one special related record

I have two tables, project and photo. photo has ID,projectID,path : each project has multiple photos.

How to represent one special related record

I have two tables, project and photo. photo has ID,projectID,path : each project has multiple photos.

Is it substandard if I have multiple tables in my database yet there’s no relationship at all? [closed]

Closed 10 years ago.

Using a single table for identity and metadata

I’m in the early design phase of a project to provide an e-commerce platform that will require several entities to be modelled, products, customers, orders, CMS pages, etc. They will all have a few things in common (ID, creation timestamp, last modified timestamp, etc).