Since you run it successfully without an issue but I keep running into issue I am suspecting if there is a difference between mysql and aurora mysql on this. The engine is developed based on mysql community version. Per AWS aurora mysql should be 100% compatible with mysql. I am using aws aurora mysql instead of mysql directly. The below is the one based on your suggestion – changeset your.name:101 end-delimiter:$$ – changeset your.name:101 end-delimiter:"$$" … 64 common frames the change with the below combinations ( totally 4 cases) – changeset your.name:101 end-delimiter:/Ĭaused by: : You have an error in your SQL syntax check the manual that corresponds to your MySQL server version for the right syntax to use near ‘’ at line 10 [Failed SQL: (1064) – changeset your.name:101 end-delimiter:/Īt $ExecuteStatementCallback.doInStatement(JdbcExecutor.java:397)Īt .execute(JdbcExecutor.java:83)Īt .execute(JdbcExecutor.java:151)Īt (AbstractJdbcDatabase.java:1279)Īt (AbstractJdbcDatabase.java:1261)Īt (ChangeSet.java:661) Thanks MikeOliva and it to below as suggested, the issue is still the same Reason: : You have an error in your SQL syntax check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 10 [Failed SQL: (1064) - changeset your.name:101 end-delimiter:/Īt (ChangeLogIterator.java:126)Īt $null$0(Liquibase.java:265)Īt $child$0(Scope.java:180)Īt $update$1(Liquibase.java:264)Īt (Liquibase.java:2405)Īt (Liquibase.java:211)Īt (Liquibase.java:197)Īt .performUpdate(SpringLiquibase.java:314)Īt .afterPropertiesSet(SpringLiquibase.java:269)Īt .(AbstractAutowireCapableBeanFactory.java:1863)Īt .(AbstractAutowireCapableBeanFactory.java:1800)Ĭaused by: : Migration failed for change set classpath:db/changelog/aurora-mysql/changelog.yml::2::N627756: Thanks Caused by: : : Migration failed for change set classpath:db/changelog/aurora-mysql/changelog.yml::2::N627756: Unfortunately I have seen a clear analysis on this issue and the issue raiser confirmed his/her issue was resolved.Ĭould anyone please shed me some light how to address this issue? There were a few similar questions posted earlier. Apparently after the delimiter is specified whenever it meets semicolon the error was thrown. However when it is deployed I am still getting the below exception. The function creation works well on mysql workbench. To be more specific it is aws aurora mysql - changeset your.name:101 end-delimiter:/ I am using mysql 5.7 and liquibase is 4.10.0. This time I used the official end-delimiter sample from end-delimiter SQL attribute | Liquibase Docs as the template to build my file as below My original post yesterday was detected by the robot as a potential spam and has been released by admin This is the second time I post this question. Line 14 is INSERT INTO tbl_timeseries_audit (id, action, name, description, datasource, ticker, field, frequency, currency, lag, deleted, version, updated_by ,updated_dt) values ( NEW.id, 'INSERT', NEW.name, NEW.description, NEW.datasource, NEW.ticker, NEW.field, NEW.frequency, NEW.currency, NEW.lag, NEW.deleted, NEW.version, NEW.updated_by, New.update_dt) Ĭould anyone please shed some light? Where is that ‘’ coming from? Got the error “Caused by: 圎rrorException: You have an error in your SQL syntax check the manual that corresponds to your MySQL server version for the right syntax to use near ‘’ at line 14” , rollback drop trigger tbl_timeseries_au INSERT INTO tbl_timeseries_audit (id, action, name, description, datasource, ticker, field, frequency, currency, lag, deleted, version, updated_by ,updated_dt) values ( NEW.id, 'UPDATE', NEW.name, NEW.description, NEW.datasource, NEW.ticker, NEW.field, NEW.frequency, NEW.currency, NEW.lag, NEW.deleted, NEW.version, NEW.updated_by, New.update_dt) rollback drop trigger tbl_timeseries_ai INSERT INTO tbl_timeseries_audit (id, action, name, description, datasource, ticker, field, frequency, currency, lag, deleted, version, updated_by ,updated_dt) values ( NEW.id, 'INSERT', NEW.name, NEW.description, NEW.datasource, NEW.ticker, NEW.field, NEW.frequency, NEW.currency, NEW.lag, NEW.deleted, NEW.version, NEW.updated_by, New.update_dt) The below is sql - liquibase formatted sql Have been fighting with this for a a little, still cannot figure out what is wrong
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |