|There's more than one way to do things|
database design questionby nop (Hermit)
|on Feb 07, 2003 at 10:54 UTC||Need Help??|
nop has asked for the
wisdom of the Perl Monks concerning the following question:
I'm working on a database app that generates web content for third-party sites. The same general content is often pushed to multiple (between 3 and 10) third-party sites. These 3rd party partner sites accept content in various ways: some through flat text feeds, some through XML, etc. For the same general submission, each partner requires (slightly) different data in a slightly different format (some take two fields, some three or four; some take wider lines, some shorter; etc). On my side, I store the generic submission concept in our database. What I also want to store is, for each specific submission, the actual submission sent to each partner. There's no hope I could get the partners to agree on a standard submission format; I'm stuck with catering to each of their particularities.
Here are the options I've considered:
Any suggestions from the gang most highly appreciated.
And if XML is the way to go, any comments on smart vs. dumb ways to encode via XML appreciated.