K
Karstens Rage
Sorry if this is a issue that has been discussed before but I am not
even sure how to search for something like this.
Say I have something that is very vague in terms of its definition. Like
maybe a purchase order from a customer. Each customer defines its PO
in terms of an XML schema or DTD which is specific but different for
each customer. Also I don't know ahead of time all the customers' DTD's.
I also have my own specification for how I store customer ID's and dates
and inventory, etc. and I want to put that into a relational database to
allow for all the benefits therein.
So rather than try to force the arbitrary XML into some flexible
database schema, is the standard practice to just store the XML along
with the DB record as a BLOB? What are other options that people/service
use?
In the front end and middle layer, XML is passed around but I eventually
need to store stuff in the backend. I am concerned about having to
constantly modify the database schema in the backend due to unforseen
stuff that I have to account for in the front end. Also I don't want to
have to try and design everything up front to account for anything that
might come along.
Any comments or pointers to discussions that already address this
greatly appreciated.
k
even sure how to search for something like this.
Say I have something that is very vague in terms of its definition. Like
maybe a purchase order from a customer. Each customer defines its PO
in terms of an XML schema or DTD which is specific but different for
each customer. Also I don't know ahead of time all the customers' DTD's.
I also have my own specification for how I store customer ID's and dates
and inventory, etc. and I want to put that into a relational database to
allow for all the benefits therein.
So rather than try to force the arbitrary XML into some flexible
database schema, is the standard practice to just store the XML along
with the DB record as a BLOB? What are other options that people/service
use?
In the front end and middle layer, XML is passed around but I eventually
need to store stuff in the backend. I am concerned about having to
constantly modify the database schema in the backend due to unforseen
stuff that I have to account for in the front end. Also I don't want to
have to try and design everything up front to account for anything that
might come along.
Any comments or pointers to discussions that already address this
greatly appreciated.
k