Re: MySQL: DB Design for tags and items
> I want Users to have private and public keys.
If a tag can have a different userID from its parent item, tags.userID makes sense, otherwise not.
> is this good in terms of scaling with website.
It's standard parent-child architecture.
Unless you anticipate quadillions of extraterrestrial users, userID bigint is overkill; int unsigned will cover more than half the people on the planet.
Subject
Written By
Posted
Re: MySQL: DB Design for tags and items
July 22, 2015 09:42AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.