2014.10.28 MSS Code Factory 1.11.12527 Service Pack 5 adds core Chain support, corrects SQL Server and MySQL defects

Due to the number of existing bugs I corrected while working on the Chain support
to date, I've decided to issue Service Pack 5 at this time.  I'll inject another
service pack with the remaining Chain implementation at some point in the future.
Not that I expect it to take very long to complete the remaining tasks, but this
release is 100% backwards compatible with SP4 and lets you specify Chain support
without breaking the old functionality.

All of the databases now pass the full suite of CFDbTest 2.0 tests, with the exception
of MySQL, which fails some tests due to it not supporting the full date-time range
that Java allows.

The sizes of some of the CFSecurity 2.0 strings have been reduced so that there are
no longer errors produced when installing a MySQL database server schema.  I don't
think it's an unreasonable restriction to limit things like JEE mount points, user
email addresses, and cluster addresses to 192 characters.

Worth noting is that SQL Server now passes the delete security tests that it has
been failing for a few months.  It turned out I wasn't checking for errors properly
for delete operations in the JDBC code.  This additional error checking is one of
the key reasons I decided to issue this current Service Pack 5 release.

When create or delete operations are performed with chained data, the previous and
next objects in the chain are updated for atomic operations, but not for delete-by-index
operations.  However, seeing as you have to do a beginEdit() which forces a read from
the database before allowing you to manipulate data, most code should be safe even
if chains are being used.  Otherwise after doing a delete-by-index you should refresh
the chain members using the index-by-container-key forced read to ensure that the cached
chain information is in sync.  Alternatively, you could simply flush the entire cache
for the affected object(s) and let them be re-read if you're not sure which container
keys have been affected by the operation.