liquibase.exception.DatabaseException: Error executing SQL INSERT INTO public.databasechangelog (ID, AUTHOR, FILENAME, DATEEXECUTED, ORDEREXECUTED, MD5SUM, DESCRIPTION, COMMENTS, EXECTYPE, LIQUIBASE) VALUES ('1', 'jason', 'jar:file:/Users/toby/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/com.semantico.journals.frontend/WEB-INF/lib/sipp2-locator-1.0-SNAPSHOT.jar!/database/scripts/00-locator-liquibase.sql', NOW(), 2, '7:b6b832985892bbec4f63b3e4ec0c949c', 'The ''sql'' tag allows you to specify whatever sql you want. It is useful for complex changes that aren''t supported through Liquibase''s automated refactoring tags and to work around bugs and limitations of Liquibase. The SQL contained in the sql tag...', '', 'EXECUTED', '3.0.0-SNP'): ERROR: value too long for type character varying(200)

JIRA | Toby Cole | 3 years ago
  1. 0

    When using SpringLiquibase, the file names used for the databasechangelog can get rather long as it can use resource paths within jar files, e.g. {code}jar:file:/Users/toby/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/com.project.name/WEB-INF/lib/some-library.jar!/database/scripts/00-project-database-liquibase.sql{code} When these paths exceed 200 characters, liquibase fails with the following stack trace: {code:java} liquibase.exception.DatabaseException: Error executing SQL INSERT INTO public.databasechangelog (ID, AUTHOR, FILENAME, DATEEXECUTED, ORDEREXECUTED, MD5SUM, DESCRIPTION, COMMENTS, EXECTYPE, LIQUIBASE) VALUES ('1', 'jason', 'jar:file:/Users/toby/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/com.semantico.journals.frontend/WEB-INF/lib/sipp2-locator-1.0-SNAPSHOT.jar!/database/scripts/00-locator-liquibase.sql', NOW(), 2, '7:b6b832985892bbec4f63b3e4ec0c949c', 'The ''sql'' tag allows you to specify whatever sql you want. It is useful for complex changes that aren''t supported through Liquibase''s automated refactoring tags and to work around bugs and limitations of Liquibase. The SQL contained in the sql tag...', '', 'EXECUTED', '3.0.0-SNP'): ERROR: value too long for type character varying(200) at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:56) ~[liquibase-core-3.0.2.jar:na] at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:98) ~[liquibase-core-3.0.2.jar:na] at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:64) ~[liquibase-core-3.0.2.jar:na] at liquibase.database.AbstractJdbcDatabase.markChangeSetExecStatus(AbstractJdbcDatabase.java:1209) ~[liquibase-core-3.0.2.jar:na] at liquibase.changelog.visitor.UpdateVisitor.visit(UpdateVisitor.java:34) ~[liquibase-core-3.0.2.jar:na] at liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:58) ~[liquibase-core-3.0.2.jar:na] at liquibase.Liquibase.update(Liquibase.java:135) ~[liquibase-core-3.0.2.jar:na] at liquibase.integration.spring.SpringLiquibase.performUpdate(SpringLiquibase.java:285) ~[liquibase-core-3.0.2.jar:na] at liquibase.integration.spring.SpringLiquibase.afterPropertiesSet(SpringLiquibase.java:258) ~[liquibase-core-3.0.2.jar:na] [… spring setup truncated] {code} Suggested fix: update filename to 400 characters (merge request on the way).

    JIRA | 3 years ago | Toby Cole
    liquibase.exception.DatabaseException: Error executing SQL INSERT INTO public.databasechangelog (ID, AUTHOR, FILENAME, DATEEXECUTED, ORDEREXECUTED, MD5SUM, DESCRIPTION, COMMENTS, EXECTYPE, LIQUIBASE) VALUES ('1', 'jason', 'jar:file:/Users/toby/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/com.semantico.journals.frontend/WEB-INF/lib/sipp2-locator-1.0-SNAPSHOT.jar!/database/scripts/00-locator-liquibase.sql', NOW(), 2, '7:b6b832985892bbec4f63b3e4ec0c949c', 'The ''sql'' tag allows you to specify whatever sql you want. It is useful for complex changes that aren''t supported through Liquibase''s automated refactoring tags and to work around bugs and limitations of Liquibase. The SQL contained in the sql tag...', '', 'EXECUTED', '3.0.0-SNP'): ERROR: value too long for type character varying(200)
  2. 0

    When using SpringLiquibase, the file names used for the databasechangelog can get rather long as it can use resource paths within jar files, e.g. {code}jar:file:/Users/toby/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/com.project.name/WEB-INF/lib/some-library.jar!/database/scripts/00-project-database-liquibase.sql{code} When these paths exceed 200 characters, liquibase fails with the following stack trace: {code:java} liquibase.exception.DatabaseException: Error executing SQL INSERT INTO public.databasechangelog (ID, AUTHOR, FILENAME, DATEEXECUTED, ORDEREXECUTED, MD5SUM, DESCRIPTION, COMMENTS, EXECTYPE, LIQUIBASE) VALUES ('1', 'jason', 'jar:file:/Users/toby/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/com.semantico.journals.frontend/WEB-INF/lib/sipp2-locator-1.0-SNAPSHOT.jar!/database/scripts/00-locator-liquibase.sql', NOW(), 2, '7:b6b832985892bbec4f63b3e4ec0c949c', 'The ''sql'' tag allows you to specify whatever sql you want. It is useful for complex changes that aren''t supported through Liquibase''s automated refactoring tags and to work around bugs and limitations of Liquibase. The SQL contained in the sql tag...', '', 'EXECUTED', '3.0.0-SNP'): ERROR: value too long for type character varying(200) at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:56) ~[liquibase-core-3.0.2.jar:na] at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:98) ~[liquibase-core-3.0.2.jar:na] at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:64) ~[liquibase-core-3.0.2.jar:na] at liquibase.database.AbstractJdbcDatabase.markChangeSetExecStatus(AbstractJdbcDatabase.java:1209) ~[liquibase-core-3.0.2.jar:na] at liquibase.changelog.visitor.UpdateVisitor.visit(UpdateVisitor.java:34) ~[liquibase-core-3.0.2.jar:na] at liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:58) ~[liquibase-core-3.0.2.jar:na] at liquibase.Liquibase.update(Liquibase.java:135) ~[liquibase-core-3.0.2.jar:na] at liquibase.integration.spring.SpringLiquibase.performUpdate(SpringLiquibase.java:285) ~[liquibase-core-3.0.2.jar:na] at liquibase.integration.spring.SpringLiquibase.afterPropertiesSet(SpringLiquibase.java:258) ~[liquibase-core-3.0.2.jar:na] [… spring setup truncated] {code} Suggested fix: update filename to 400 characters (merge request on the way).

    JIRA | 3 years ago | Toby Cole
    liquibase.exception.DatabaseException: Error executing SQL INSERT INTO public.databasechangelog (ID, AUTHOR, FILENAME, DATEEXECUTED, ORDEREXECUTED, MD5SUM, DESCRIPTION, COMMENTS, EXECTYPE, LIQUIBASE) VALUES ('1', 'jason', 'jar:file:/Users/toby/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/com.semantico.journals.frontend/WEB-INF/lib/sipp2-locator-1.0-SNAPSHOT.jar!/database/scripts/00-locator-liquibase.sql', NOW(), 2, '7:b6b832985892bbec4f63b3e4ec0c949c', 'The ''sql'' tag allows you to specify whatever sql you want. It is useful for complex changes that aren''t supported through Liquibase''s automated refactoring tags and to work around bugs and limitations of Liquibase. The SQL contained in the sql tag...', '', 'EXECUTED', '3.0.0-SNP'): ERROR: value too long for type character varying(200)
  3. 0

    jhipster abstract class configuration in changelog.xml

    GitHub | 2 years ago | houcine8
    liquibase.exception.DatabaseException: org.postgresql.util.PSQLException: ERREUR: la relation ½ AbstractLinkPK ╗ existe dÚjÓ
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Liquibase primary key is created twice on H2

    Stack Overflow | 12 months ago | Newbie
    liquibase.exception.DatabaseException: org.h2.jdbc.JdbcSQLException: Ograniczenie "PRIMARY" już istnieje Constraint "PRIMARY" already exists; SQL statement: ALTER TABLE PUBLIC.ENUM_DESCENT ADD CONSTRAINT "PRIMARY" PRIMARY KEY (descent_of_disease) [90045-187] at liquibase.executor.jvm.JdbcExecutor$ExecuteStatementCallback.doInStatement(JdbcExecutor.java:316) ~[liquibase-core-3.3.2.jar:na] at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:55) ~[liquibase-core-3.3.2.jar:na] at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:122) ~[liquibase-core-3.3.2.jar:na]
  6. 0

    updating user entity to add foreign key

    GitHub | 9 months ago | francisyuya
    liquibase.exception.DatabaseException: Can't create table '.\blog\#sql-784_3f.frm' (errno: 150) [Failed SQL: ALTER TABLE blog.jhi_user ADD CONSTRAINT fk_user_activityField FOREIGN KEY (activity_field_info_id) REFERENCES blog.activity_field_info (id)]

  1. tvrmsmith 2 times, last 3 months ago
  2. tvrmsmith 7 times, last 3 months ago
  3. Malcshour 26 times, last 6 months ago
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis

  1. liquibase.exception.DatabaseException

    Error executing SQL INSERT INTO public.databasechangelog (ID, AUTHOR, FILENAME, DATEEXECUTED, ORDEREXECUTED, MD5SUM, DESCRIPTION, COMMENTS, EXECTYPE, LIQUIBASE) VALUES ('1', 'jason', 'jar:file:/Users/toby/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/com.semantico.journals.frontend/WEB-INF/lib/sipp2-locator-1.0-SNAPSHOT.jar!/database/scripts/00-locator-liquibase.sql', NOW(), 2, '7:b6b832985892bbec4f63b3e4ec0c949c', 'The ''sql'' tag allows you to specify whatever sql you want. It is useful for complex changes that aren''t supported through Liquibase''s automated refactoring tags and to work around bugs and limitations of Liquibase. The SQL contained in the sql tag...', '', 'EXECUTED', '3.0.0-SNP'): ERROR: value too long for type character varying(200)

    at liquibase.executor.jvm.JdbcExecutor.execute()
  2. Liquibase Core
    SpringLiquibase.afterPropertiesSet
    1. liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:56)[liquibase-core-3.0.2.jar:na]
    2. liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:98)[liquibase-core-3.0.2.jar:na]
    3. liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:64)[liquibase-core-3.0.2.jar:na]
    4. liquibase.database.AbstractJdbcDatabase.markChangeSetExecStatus(AbstractJdbcDatabase.java:1209)[liquibase-core-3.0.2.jar:na]
    5. liquibase.changelog.visitor.UpdateVisitor.visit(UpdateVisitor.java:34)[liquibase-core-3.0.2.jar:na]
    6. liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:58)[liquibase-core-3.0.2.jar:na]
    7. liquibase.Liquibase.update(Liquibase.java:135)[liquibase-core-3.0.2.jar:na]
    8. liquibase.integration.spring.SpringLiquibase.performUpdate(SpringLiquibase.java:285)[liquibase-core-3.0.2.jar:na]
    9. liquibase.integration.spring.SpringLiquibase.afterPropertiesSet(SpringLiquibase.java:258)[liquibase-core-3.0.2.jar:na]
    9 frames