MySQL vs for()
#2

Sorry what? I'm not really following. It sounds like your tables aren't properly normalized. If you have many maps and each map can have many objects then you need two tables: one that declares the map properties (id, name, author, creation date, whatever) and another one that is linked to it that stores the actual objects (id, mapid, modelid, x, y, z, ...).
Reply


Messages In This Thread
MySQL vs for() - by corne - 14.12.2016, 15:34
Re: MySQL vs for() - by Vince - 14.12.2016, 16:04
Re: MySQL vs for() - by PrO.GameR - 14.12.2016, 19:38
Re: MySQL vs for() - by SickAttack - 14.12.2016, 19:46
Re: MySQL vs for() - by CodeStyle175 - 14.12.2016, 20:22
Re: MySQL vs for() - by NeXoR - 14.12.2016, 20:33
Re: MySQL vs for() - by SickAttack - 14.12.2016, 21:18
Re: MySQL vs for() - by NeXoR - 15.12.2016, 17:24
Re: MySQL vs for() - by SickAttack - 16.12.2016, 00:14
Re: MySQL vs for() - by corne - 17.12.2016, 12:05

Forum Jump:


Users browsing this thread: 1 Guest(s)