Database design - normalisation help

purpleI

Hi all,

I am developing a very basic website which allows users to crfeate an advertisement, edit this ad and then renew.

The basic strucutre of the Db is:

Advert(AdID, displayData, cost, title)
Images (ImageID, AdID)
User(UserID, AdID,email, password)

One user can upload any number of adverts. He/she also creates their own password. Each ad has upto 3 images.

Any suggestions???

Thanks in advance

Kerant

Wouldn't it be best to have the UserID in the Advert table, as opposed to the AdID in the User table?

If you have the AdID in the User table you are assuming each user is going to create an advert, which I would imagine isn't always going to be true, so there is a potential for null data there.

Weedpacket

Kerant wrote:
If you have the AdID in the User table you are assuming each user is going to create an advert, which I would imagine isn't always going to be true, so there is a potential for null data there.

In fact, it's assuming that each user is going to have no more than one advert - and that an advert may be created by more than one user. Quite the opposite of what's intended, I think.

Kerant

Weedpacket;10896486 wrote:
In fact, it's assuming that each user is going to have no more than one advert - and that an advert may be created by more than one user. Quite the opposite of what's intended, I think.

Very true, there is that as well.