Multibyte characters in journal issue causes values too large for SQL column
The journal issue is constrained to 32 characters in the schema but the SQL database (Oracle in production) uses a maximum length 32 bytes, not 32 characters.
Simplest thing will be adding a check in Deposit code for 32 bytes and failing deposit. Alternatively we may be able to expand the column size in the database but we prefer not to as it's a very large table.
submission: 1505849291; DOI: 10.52065/2520-6877-2021-244-1-5-12, org.springframework.jdbc.UncategorizedSQLException: PreparedStatementCallback; uncategorized SQLException for SQL [INSERT INTO atypon.citation_info (CITATIONID, JOURNALCITEID, BOOKCITEID, SERIESTITLEID, MISSPELLINGID, SUBMISSIONID, VERSION, YEAR, VOLUME, ISSUE, SUPPLEMENT, PAGE, AUTHOR, COMPONENTNUMBER, EDITIONNUMBER, OWNERPREFIX, ARTICLETITLE, SEQUENCENUMBER, TYPE, DOI, MDCONFLICTID, PAGEMOD, SRCTYPE, ORIGPAGE, LASTPAGE, PUBMONTH, PUBDAY, CONFNAMEID, INSTCITEID, FORCEDALIASID, ALIASID, SRCSUBTYPE, LASTUPDATE, REFSUBMISSIONID, MASK) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]; SQL state [72000]; error code [12899]; ORA-12899: value too large for column "ATYPON"."CITATION_INFO"."ISSUE" (actual: 43, maximum: 32)\n; nested exception is java.sql.SQLException: ORA-12899: value too large for column "ATYPON"."CITATION_INFO"."ISSUE" (actual: 43, maximum: 32)\n
Submission id 1505849291:
<issue>Труды БГТУ Серия 5 №1 (244)</issue>
Happened 76 times in the past hour but otherwise low volume.
Expected behavior
How urgent
Definition of ready
-
Product owner: @SaraBowman -
Tech lead: -
Service:: or C:: label applied -
Definition of done updated -
Acceptance testing plan: -
Weight applied
Definition of done
-
Unit tests identified, implemented, and passing -
Code reviewed -
Available for acceptance testing via a staging URL, or otherwise -
Consider any impacts to current or future architecture/infrastructure, and update specifications and documentation as needed -
Knowledge base reviewed and updated -
Public documentation reviewed and updated -
Acceptance criteria met -
AC 1 -
AC 2
-
-
Acceptance testing passed -
Deployed to production
Notes
Edited by Patrick Polischuk