Moving this to the developers list. @Saptarshi, does this play into the work you're doing to make us work on all databases?
-Darius On Fri, Sep 9, 2011 at 9:57 AM, Jeremy Keiper <[email protected]> wrote: > Ah, I figured it out. > > In MySQL, a BLOB column maxes out at 65,535 bytes. The template property > on Form#15 is 67,389 bytes long. In Oracle, the default size for a blob is > (I think) 4GB. PostgreSQL barely supports BLOB; they use an apparently > infinite-length BYTEA. I guess I should use a <modifySql> block to change > BLOB to MEDIUMBLOB for MySQL. > > Since 1.9 isn't out yet, I assume making this change in the original > changeset is okay ... besides, the subsequent changeset will not run > properly if a resource is over the size limit. Right? > > Jeremy Keiper > OpenMRS Core Developer > AMPATH / IU-Kenya Support > > > On Thu, Sep 8, 2011 at 4:40 PM, Jeremy Keiper <[email protected]> wrote: > >> Now I get the same error as Michael: >> >> >> - Unable to update the database. See server error logs for the full >> stacktrace. >> - There was an error while updating the database to the latest. file: >> liquibase-update-to-latest.xml. Error: Migration failed for change set >> liquibase-update-to-latest.xml::201103152243-b::jkeiper: >> - Reason: liquibase.exception.UnexpectedLiquibaseException: >> liquibase.exception.CustomChangeException: Unable to copy form metadata to >> form attributes table: >> - Caused By: liquibase.exception.CustomChangeException: Unable to copy >> form metadata to form attributes table: >> - Caused By: Unable to copy form metadata to form attributes table: >> - Caused By: Data truncation: Data too long for column 'value' at row >> 1 >> >> >> Jeremy Keiper >> OpenMRS Core Developer >> AMPATH / IU-Kenya Support >> >> _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
