On 2012-08-15 1:54 PM, Rajeev Prasad wrote:
> I have to keep this data in MySql, and i am not sure (as SQL/databse is not my field)
> how to organise this into one or many tables? right now I would represent my info as
> dev_x | 1234 |1234 |184.108.40.206 |220.127.116.11 |data_specific_to_x
> |SVC_A,SVC_B,SVC_C... |dev_y,dev_z,dev_n,dev_m...
> dev_y | 2348 |7734 |10.2.3.4 |18.104.22.168
> |data_specific_to_y.....|SVC_B,SVC_X... |dev_x,dev_m...
> dev_z | 3934 |5634 |22.214.171.124 |126.96.36.199
> |data_specific_to_z.....|SVC_M |dev_n,dev_m...
> pl advice. what would be the best design? data_specific_to_device could be more than
> one column, as i get to explore the data a bit more.
> and do i really need a device_id field? whi. ch any SQL table normally has.
Without a primary key, a table isn't really a table. A surrogate
(auto_increment) PK might be simplest.
If the associated_service column is a list of values, it needs to be
projected to a child table (parentkey, data item ...).
From the info posted, I can't tell much about the other fields