Announcement

Collapse
No announcement yet.

BUG: Metadata collision whem migrating to v3.5.x

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • BUG: Metadata collision whem migrating to v3.5.x

    Context:
    We defined in Mirth v3.4.2 a meta-data for a channel, which is called "CASE" and displays the admission id in the dashboard. When migrating a channel containing this custom meta-data to v3.5.x, this is flawlessly accepted.

    Trigger:
    However, as soon as the channel is deployed, it remains in the state "deploying", throws an exception and can only be stopped by stopping the service:
    Code:
    com.mirth.connect.donkey.server.data.DonkeyDaoException: Failed to add meta-data column
    [...]
    java.sql.SQLSyntaxErrorException: Syntax error: Encountered "CASE" at line 1, column 32.
    [...]
     ERROR 42X01: Syntax error: Encountered "CASE" at line 1, column 32.
    Finding:
    If a custom metadata is named like a reserved SQL command, the adverse behavior occurs.


    Workaround:
    As soon as the concerned custom metadata column is renamed, the deployment and start of the channel works as intended.

    Environment:
    • Mirth 3.5.1
    • Windows Server 2012R2
    • Java 8
    • Derby DB
    Attached Files
Working...
X