Neo wrote:
> > i list my sql code here table device: CREATE TABLE `equ` ( ....
>
> There is no simple, normalized and NULL-less solution to your problem
> with a RMDB. If you could post some actual data, I can show how dbd
> handles it and one of the RM experts can design a schema that meets
> your needs. What exactly are you needs? Are you trying to avoid NULLs
> and or redundant data or more than X number of tables?
the model is simple i hava device and every device has there own
attributes and also the device type should be one of device's
attibute.but the point is every type has there own attributes. so i
do't know how to modeling this.
i need avoid NULLs and redundant both.
thanks for any help!
Received on Thu Jul 20 2006 - 20:05:56 CDT
