Re: schema optimization
As Peter mentioned, storing "param1...param9" as separate columns is enormously ineffective. You probably need a property relationship table that references back to this one, likely with just three fields (entity_id bigint (from this table), param_id tinyint (reference to parameters table or just a number), value int, primary key (entity_id,param_id))
The same likely applies to jail_broken though I'm not sure what you're doing there.
also | ip | int(32) | NO | | NULL | | there is no such data type as int(32), int can only go up to 11 display width max, any higher would be for zerofill only. an ipv4 which i'm guessing this is must be stored in INT(10) UNSIGNED, or alternately as BINARY(4) in a mixed (varbin) column with ipv6 addresses that are BINARY(16).
Subject
Written By
Posted
Re: schema optimization
July 23, 2012 12:56PM
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.