> I have pushed out a bunch of changes to the JpaTicketRegistry documentation. > For any one who is interested please take a look and review.
I just got a chance to carefully review this. Your additions and changes look good in general. I reoganized some of the MySQL content into a new section called "Platform-Specific Considerations" since some of the discussion only applies to MySQL and there are conceivably additional issues for other platforms we may want to discuss (e.g. abyssmal deadlock behavior on PG). I'd also like to point out that I added an important platform-specific note for MySQL regarding InnoDB tables. I added this section based on past experience and a recent discovery. From past experience I can say that you're much more likely to have orphaned tickets using MyISAM tables since the FK constraints are not enforced (http://dev.mysql.com/doc/refman/5.1/en/ansi-diff-foreign-keys.html). My recent discovery adds to that in the locking semantics required by the code around the locks table (SELECT ... FOR UPDATE) only works on InnoDB (http://dev.mysql.com/doc/refman/5.1/en/innodb-locking-reads.html). Everyone that's using MySQL in an non-trivial environment should carefully consider switching to InnoDB. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
