Is it "good db design"to have the same Id in two different tables??

[D-flyer]

Hello,

In my db design i got the following:
tblParty
partyID
..
..
lID

tblLocation
locId
..
..
..
pID

tblOrganisation
orgID
...
...
...
pID

tblPlaces
placeID
placeName
stateID

tblStates
stateID
statename

Is it "good db design"to have the pID(=placeId) in two different tables??

Any suggetions or comments are welcome.

Greetz,
D-flyer

[Defender1]

if i remember my normalization rules, placing similar columns in 2 tables is good if you need to perform joins on those 2 tables.

[D-flyer]

Sorry but my aim is not to join the 2 tables

I just thought the location of a party can be different from the location of the organisation and by placing the place-names in a seperate table i can reuse some of those place-names.

Btw: The table that join the whole db is the tblParty

[Stefan Holmberg]

Well since the two PID:s have different meaning ( place for organisation and place for organisation ) then you have no redundant data - instead as you say by doing this you can reuse the placenames = good design!

Another comment ( not because anyone would care ): It is considered correct to have a table name in singularis ( not tblPlaces but tblPlace )

[D-flyer]

thx, stefan