> > Yes, that's one of the much-stated benefits - and it's a very > compelling one - but if you change the structure of a document you > still have to change code for it to DO anything.
Yes, I get that, but with the DAO/Service/Bean approach, it seems like I have more layers needed to be changed. I'm just exploring if there're any other lighter/more flexible approach to this. Since I'm using MongoDB, the results from the driver (i.e. http://mongocfc.riaforge.org/) is already in struct or array. I'm just wondering if I can just use them and accelerate the development time, while keep code as clean as possible. Not that I'm really in love with dealing only with data (struct/array), just thinking out loud, and what could I have done better. Thanks, Henry On Fri, Jan 7, 2011 at 11:35 AM, Barney Boisvert <[email protected]>wrote: > > Ya, the thing is, docs in noSql are quite dynamic (no fixed schema) and > > should be easy to change. > > Yes, that's one of the much-stated benefits - and it's a very > compelling one - but if you change the structure of a document you > still have to change code for it to DO anything. I.e. your code is > still dependant on the data in the DB, you just are absolved from a) > forcing every instance of a collection to have identical fields, and > b) formalizing data structure changes with DDL. > > For example, say I want to add a URL slug to my contrived blog app. > Yes, I can just start throwing 'slug' attributes into my entries in my > database, but they don't do anything until I expose that data in the > application (probably editing, but certainly storing at creat time and > use for post selection). > > Short answer, regardless of your storage mechanism, if your data > changes your application must change. > > Of the two points I listed above, I personally thing than 'a' is of > FAR greater benefit than 'b'. It's ridiculously powerful to just > throw extra stuff on some entities in your collection without having > to consider the rest of the collection. You, of course, have to wrap > it with some business logic for identifying which entities are > "special" in that way, but being able to just toss stuff in there is > the big win of schema-less data stores. > > cheers, > barneyb > > On Fri, Jan 7, 2011 at 11:02 AM, Henry Ho <[email protected]> wrote: > > Barney B, > > Ya, the thing is, docs in noSql are quite dynamic (no fixed schema) and > > should be easy to change. > > Maybe you're right. When it comes to change, with the Bean/DAO/Service > way, > > I had to change the DAO and Bean, but at least the view layer doesn't > have > > to change, much. > > With plain old struct, I can minimize the changes of Bean/DAO, and just > > update the Service layer and 'leak' the change(s) into the View layer. > > Pick my poison I guess? > > > > > > Henry > > > > -- > Barney Boisvert > [email protected] > http://www.barneyb.com/ > > -- > You received this message because you are subscribed to the Google Groups > "CFCDev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<cfcdev%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/cfcdev?hl=en. > > -- You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en.
