Sent from my iPad
On 2013-01-15, at 6:38 AM, James Cicenia <ja...@jimijon.com> wrote: > That sounds like a NoSQL type database. > > Speaking of which, does WO support those? I haven't written SQL in years, so it must! :) > > > On Jan 15, 2013, at 8:33 AM, Jesse Tayler <jtay...@oeinc.com> wrote: > >> not to throw a wrench, >> >> but I would NOT store XML data but rather, >> >> I would use a key-table design where you can simply add arbitrary keys to >> things like this using queries and relationships. >> >> I once did a system for restaurant menus that had to understand the type of >> object (salad) would have a choice of dressing, but a caesar would not and a >> potato would have a choice of other things or whatever else. There were >> structures, but also an exception to every rule really. Kind of a challenge. >> >> basically, I'd watch out for putting structured data into the database and >> would suggest considering a flat table structure instead. >> >> you'd likely still want custom components to handle your UI because it >> sounds important, but I would just consider how a database can store data >> that is unformatted and unstructured and I'd add the xml structures to it at >> another layer. >> >> hope that helps! >> >> >> On Jan 15, 2013, at 7:18 AM, Flavio Donadio <fla...@donadio.com.br> wrote: >> >>> >>> On 13/01/2013, at 07:12, Paul Hoadley wrote: >>> >>>> I suppose it depends how frequently you expect the template XML to change, >>>> if at all, and whether you envisage changing it on the fly, or if you >>>> could just restart the application to pick it up from properties or a text >>>> file. Never changes? You could use text files (in Resources, or >>>> downloadable from somewhere, say S3) that are picked up during application >>>> initialisation. Changes frequently and is user-editable? Store it in the >>>> database—perhaps an XMLTemplate entity, one for each template type. So >>>> many options. >>> >>> Yea, Paul. I am inclined to store the template XML in the database. Since >>> the template is the same for every product in a given category, I am going >>> to store the template in a property of the ProductCategory entity. >>> >>> The template will change from time to time, especially when new products >>> bring different features that need to be included in it. >>> >>> But my question is: how do you guys recommend that I do to: >>> >>> 1. Generate the HTML form; and >>> >>> 2. Insert/update data in the XML so I can store it in the entity. >>> >>> I am almost certain that I will need a custom component for this. >>> >>> >>> Regards, >>> Flavio >>> _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/webobjects-dev/jtayler%40oeinc.com >>> >>> This email sent to jtay...@oeinc.com >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/james%40jimijon.com >> >> This email sent to ja...@jimijon.com > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/programmingosx%40mac.com > > This email sent to programming...@mac.com
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
