Karl Guertin wrote:
> On 8/29/06, Sylvain Hellegouarch <[EMAIL PROTECTED]> wrote:
>
>> Well be careful when suggesting an OODBMS. They are nice but have no
>> features whatsoever for querying or exporting data for instance. So
>> storing XML documents as strings within an OODBMS is not much better
>> than storing them in an RDBMS. You still cannot use XQuery or XPath
>> directly on the database. So there is lttle value really.
>>
>
> Why would you store the document as a string? You'd convert it into an
> object and store it as an object, querying it using the OODBMS query
> functionality. You do export using something like Markdown or Kid.
>
Which querying functionnality? ZODB has none. ZODB is a database not
even a full fledged OODBMS.
Now you may have your set of tools but the problem is still valid.
OODBMS have not yet a query language such as SQL. OQL never took off.
Regarding storing objects, ZODB is limited to pickable object AFAIK
therefore, even though your idea of storing objects is nice it is
limited and would certainly push you to store regular object and
transform them into XML documents when being retrieved through
ElementTree or Amara.
My point anyway is not that your solution is not valid, simply it is
more a hack (a nice one certainly).
> I've paid my xml dues (I wrote a publishing system that was XML Schema
> validated and published with XSL-T) but it was a whole lot easier to
> rewrite that system in Python. Runs faster, too.
>
Faster than what?
- Sylvain
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" 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/turbogears
-~----------~----~----~----~------~----~------~--~---
