Philipp Kamps <[email protected]> wrote on 23/06/2010 17:42: > Hi Gaetano, > > I'm sure I'm missing a lot of disadvantages - but it would do some things > better: > > Advantages > > 1) SQL gives me headaches -- xquery makes a lot more sense to me
I guess it all boils down to what you grew up learning :-) I loathe to have to learn new query languages that will possibly fade away before I even get proficient with them. So far we use sql, the ez fetch filters syntax (yuk) and the solr filter syntax (slightly better, at least wrt completeness). Do we want to add yet another one? > 2) semi structured data storage > - example: easy to add an additional attribute to one single instance of > an article without having 'ezcontentobject_attribute' explode that should be doable with any no-sql db > 3) easy to store html content Isn't this against the whole principle of eZP? > > Disadvantages > > 1) slow > and we're pretty slow as it stands now - can we afford to do worse? > > > > On Wed, Jun 23, 2010 at 5:24 PM, Gaetano Giunta<[email protected]> wrote: >> Philipp Kamps wrote: >>> What about XML DB for a content engine? http://www.basex.org >>> >> >> I thought that "xml db" as a buzzword was dead years ago... >> >> ;) >> >> Apart from the lame joke, what would be the advantages / disadvantages >> compared to the current nosql crop? >> -- >> Sdk-public mailing list >> [email protected] >> http://lists.ez.no/mailman/listinfo/sdk-public >> > -- Sdk-public mailing list [email protected] http://lists.ez.no/mailman/listinfo/sdk-public
