[wp-hackers] Restructuring Category Hierarchy

[Jamie Talbot]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael E. Hancock wrote:
> With the current design, if something borks on a server when adding or
> deleting a category, not a big deal--just causes the user to have to re-add
> or re-delete that category.
> 
> But with the Nested List, what happens in a delete case, where the server
> *coughs* just after the deletion step, but before the left and right
> pointers get reset?
> 
> When you have control of your MySQL server this is probably a moot point,
> but there's way too many hosts where I see stability problems with their
> servers.
> 
> Is that something to be concerned about?
> 
> 
> MichaelH

It is a concern - I don't use MyISAM at all outside of WordPress for this reason.  However, there
are still multiple stages in adding or deleting in the current system - we write to wp_post2cat as
well as wp_categories and wp_posts - if it borks halfway through any of that you wouldn't be happy.
 We could always use InnoDB for the new tables, which provide transaction support (as well as
referential constraints).  And there's no problem mixing the two types in the same database...  But
as is pointed out in another thread, it takes more space and is potentially slower.

Cheers,

Jamie.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGQTyjrovxfShShFARApVIAKCRNPIiR7EefFVr7uycPjRcRQ7ucgCcDqCw
tNpGl5vq3YNqvZTmGWcUWCI=
=G/W1
-----END PGP SIGNATURE-----