On Mon, Nov 25, 2013 at 8:29 AM, Steven Siebert wrote:
> Larry,
>
>
> If that's the only type of queries you're gonna make, sounds like MySQL
> can be a good solution (from an indexing perspective, those queries will be
> fine). Basically, you would be using MySQL as a read-only copy of the XML
I recently moved to a new web server (running 5.5.32) on one of my production
systems. The new server has more RAM, faster CPU, etc so we see queried results
a lot quicker. However, with basically the default my.cnf config file on each
system, we see simple inserts taking about 10x longer than o
On Mon, Nov 25, 2013 at 4:29 AM, Johan De Meersman wrote:
> ___
> | Nodes |
> |---|
> | id| ---
> | [more fields] | |
> | parent_id | >--
> |___|
>
>
> And then you join the table with itself as needed. Do note that you'll
> need a sel
Larry,
If that's the only type of queries you're gonna make, sounds like MySQL can
be a good solution (from an indexing perspective, those queries will be
fine). Basically, you would be using MySQL as a read-only copy of the XML
content...so your goal here is to understand how you'll be needing
___
| Nodes |
|---|
| id| ---
| [more fields] | |
| parent_id | >--
|___|
And then you join the table with itself as needed. Do note that you'll need a
self-join for every level you query, and that every self-join incrementally
slow
