> MySQL really wasn't designed for this sort of useage. Your selects are going
> to be brute force searches on unidexed data, which is exactly why they are so
> slow...
>
> I would advise you to look into using an XML or XML Enabled RDBMS. There are
> a lot of possible considerations here as to what you might want.
I would advise you to consider abandoning storing XML in a database entirely, as it
completely breaks the idea of database design -
namely, "don't store duplicate data". You would probably be much better served by writing
code to wrap the actual data in the
database with XML - it's quite easy, and a lot less hassle than trying to store XML.
