Katz, Dov B \(IT\) wrote: > There are several approaches to solving this type of problem, imho, and > each one has costs and benefits, and I've given each of them a "report > card" (A being best, F being worst): > > 1) Xml into a field (as originally speculated) > Benefits: flexible design, structured data once retreived > Costs: useless for searching
Unless your database supports functional indexes. > data not typed, (all strings) Unless your database supports schema validation. > storage bloat due to markup Not that bad if the database supports inline compression. Columns have overhead too. Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:245066 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
