(Note that MySQL's protocol limits would probably kick in before the
4GB limit, but you can definitely move things much bigger than 65,536
bytes in a MySQL 5.x INSERT statement.)
This change has no backwards compatibility impact (at least in MySQL)
because the database queries generated to manipulate a CLOB are
exactly the same. That means your existing database will work 100%
with no modifications with code generated from this new schema.
To take advantage of the higher limit in your existing databases,
you'll want to alter your table:
ALTER TABLE pk_context_cms_slot MODIFY value LONGTEXT;
I may come up with a handy task to do this for you at some point using
the Doctrine migration API but in the meantime it's one line of MySQL
to lift the limit.