Hi folks, Making some headway on setting up in-memory, test databases, but I've encountered a "type" problem. We currently define a couple of columns as the type LONGTEXT, because we anticipate storing really large strings of data. If I understood my reading of the Liquibase docs, it is preferred to use CLOB in order to keep the XML compatible across multiple databases. Unfortunately, CLOB creates a regular TEXT field in MySQL, thus reducing the size to 64k - yes, our data could be larger than that.
So, I'm wondering if there is a good way to handle this? Perhaps this is another good use of the "context" attribute on a changeset - so that one datatype is used for production and another is used for testing? While not ideal, it would work. I just wanted to try to get a "best practice" opinion. Thanks, Dave ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Liquibase-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/liquibase-user
