Home → Bug Reports →

Dynamic metadata length

• Edit

Donna Cannady Nall

30 Oct, 2014 04:56 PM

We need to store metadata with a character count greater than 250. When we try to insert we get the following error:

An error occurred during editing: Hibernate flushing: Could not execute JDBC batch update; uncategorized SQLException for SQL [insert into cxml_dynamicmetadatafield (name, metadataValue, owningEntityId, id) values (?, ?, ?, ?)]; SQL state [72000]; error code [12899]; ORA-12899: value too large for column "CASCADE"."CXML_DYNAMICMETADATAFIELD"."METADATAVALUE" (actual: 291, maximum: 250) ; nested exception is java.sql.BatchUpdateException: ORA-12899: value too large for column "CASCADE"."CXML_DYNAMICMETADATAFIELD"."METADATAVALUE" (actual: 291, maximum: 250)

Would it be possible to change the column limit for this field in the Cascade database? Current version is 7.10.2 with Oracle for our database. Would altering the database table cause issue with either this version or current versions of Cascade?

1. 1 Posted by Ryan Griffith on 30 Oct, 2014 05:06 PM

   

   Hi Donna,

   It does indeed look like there is a limit of 250 characters for dynamic metadata fields. I searched our issue tracker and found this improvement which would allow for more characters to be entered into those fields. I've gone ahead and moved this up in priority as it seems we've had a couple of folks run into this lately.

   To my knowledge, changing the column could potentially have a negative effect on other areas in the application, so I would advise against this.

   I don't have an ETA on when the improvement will be implemented, but you can check the release notes for any versions we make available to see if this made it in.

   Let me know if you have any further questions.

   Thanks

   • Edit

2. 2 Posted by Nall, Donna on 30 Oct, 2014 05:09 PM

   

   Thank you for the quick response and information. We really need this to work, so will watch for updates and full understanding of the ramifications.
   ___________________________
   Donna Cannady Nall
   Digital Communications Manager
   Emory University School of Law

   Office 404.727.3691
   Cell 404.964.6933

   • Edit

3. 3 Posted by Ryan Griffith on 04 Nov, 2014 08:06 PM

   

   Hi Donna,

   My apologies for the delayed response, and for the inconvenience this may be causing you.

   I was checking with the developers on whether the column size could be increased. Unfortunately, it cannot be increased due to indexes that are added for that column, which would cause the column and index sizes to differ.

   Although I do not have an official timeline for the improvement I mentioned, but I can confirm it is towards the top of our priority list for an upcoming release. Feel free to track the progress of this issue or keep an eye out for it on our Release Notes site.

   Please let me know if you have any questions.

   Thanks!

   • Edit

4. 4 Posted by Nall, Donna on 04 Nov, 2014 08:19 PM

   

   Thank you - it's really important as we digitize our academic scholarship: journal titles are really long!
   ___________________________
   Donna Cannady Nall
   Digital Communications Manager
   Emory University School of Law

   Office 404.727.3691
   Cell 404.964.6933

   • Edit

5. 5 Posted by Ryan Griffith on 04 Nov, 2014 08:30 PM

   

   Not a problem at all, Donna. I definitely agree this should be resolved to help make those fields more flexible. I'll try to re-prioritize the issue a bit higher for you.

   The only workaround I can think of would be to use a shorter version of the title for the metadata and add the full title to a data definition field. Definitely not ideal, though.

   I'm going to go ahead and close this discussion, please feel free to comment or reply to re-open if you have any additional questions.

   Have a great day!

   • Edit

6. Ryan Griffith closed this discussion on 04 Nov, 2014 08:30 PM.