Arnar Birgisson wrote: > Have you considered just storing the XML serialized in a text field? > Do you need to be able to make queries like "give me all playlists > with references to xyz.avi" or "find all nodes of type media_list"?
Well, the playlist is highly tied with the rest of the application (which I have not explained yet). The playlist application is just a "module" of the main application (client, shop and player management). It deals with clients and their shops where each shop subscribes to optionnal video content (to make it very simple). So when a player from a shop connects to our database, from the player's id, I do a bunch of joins accoss tables to find out which shop the player connects from. Then I figure out the subscribed options of the shop, generate the according XML playlist on the fly and finaly send back the "personnalized" XML to the player. That's the basic idea. > As Michael pointed out, the ElementTree example stores the XML data > en-masse, so if you don't need those kind of queries, you might see > better performance and a simpler way of life if you just serialize the > ElementTree instances to XML in a text field and vice versa. Yeah, I thought about that, but I feel it would be harder for me to do it this way. Regards, -- Alexandre CONRAD --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
