 | |
#11
 
| |||
| |||
|
Re: Database design pattern qestion -
04-27-2008
, 09:09 AM
|
I have a number of "clients" which report with a string "client_id,client_model,0001001001", when the third part is a binary string containing client's status. * Each client model can have various status message length and interpretation. *For each of the locations in the status message, stands it's description and it's "importance level". This is a **very** denormalized design. *That is about all we can say without more specs. *You have what I call an "Automobiles, Squids and Britney Spears" design -- many unrelated things forced into a single structure that mixes data and metadata together, inviolation of any kindof Normal Form. *You should handle parsing this mess in the front end before it gets to the database. *Oh, are these binary strings high- end or low-end, etc.? *Then insert the data into normalized tables. |
this. (FYI - Celko is actually an author of many good books on SQL).
Are you really Joe Celko? Woland - I'd suggest you read his books
after the Head First one. His stuff is a bit more cerebral and
requires a bit of knowledge.
#12
| |||
| |||
|
|
I have a number of "clients" which report with a string "client_id,client_model,0001001001", when the third part is a binary string containing client's status. * Each client model can have various status message length and interpretation. *For each of the locations in the status message, stands it's description and it's "importance level". This is a **very** denormalized design. *That is about all we can say without more specs. *You have what I call an "Automobiles, Squids and Britney Spears" design -- many unrelated things forced into a single structure that mixes data and metadata together, inviolation of any kindof Normal Form. *You should handle parsing this mess in the front end before it gets to the database. *Oh, are these binary strings high- end or low-end, etc.? *Then insert the data into normalized tables. |
this. (FYI - Celko is actually an author of many good books on SQL).
Are you really Joe Celko? Woland - I'd suggest you read his books
after the Head First one. His stuff is a bit more cerebral and
requires a bit of knowledge.
#13
| |||
| |||
|
|
I have a number of "clients" which report with a string "client_id,client_model,0001001001", when the third part is a binary string containing client's status. * Each client model can have various status message length and interpretation. *For each of the locations in the status message, stands it's description and it's "importance level". This is a **very** denormalized design. *That is about all we can say without more specs. *You have what I call an "Automobiles, Squids and Britney Spears" design -- many unrelated things forced into a single structure that mixes data and metadata together, inviolation of any kindof Normal Form. *You should handle parsing this mess in the front end before it gets to the database. *Oh, are these binary strings high- end or low-end, etc.? *Then insert the data into normalized tables. |
this. (FYI - Celko is actually an author of many good books on SQL).
Are you really Joe Celko? Woland - I'd suggest you read his books
after the Head First one. His stuff is a bit more cerebral and
requires a bit of knowledge.
 |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.