I believe it maybe the name of the output file has to include the type of database platform. Could you try changing migration.sql to migration.postgresql.sql
Also, you can get help on our forum (I just randomly checked here, usually don't search dev.to for liquibase issues): forum.liquibase.org/
or real-time (ish) chat on our Discord channel: discord.gg/9yBwMtj
Detailed instructions for generatechangelog, maybe it is the same for updatesql:
Running the generatechangelog command
Verify or configure the liquibase.properties file to include your driver class path, database URL, and user authentication (user name/password) information for the database you want to connect to.
Open your CLI and run the following command:
Replace with the short name of the targeted database type. These include h2, oracle, postgresql, and mysql.
The generateChangeLog command generates a changelog that contains your objects (represented as changesets) and places the file in the same directory where the command was run.
Hah! I hope it works. Once this gets resolved, I would like to understand a little more why your workflow is this way. My users typically just run a liquibase update rather than translate to sql into a file but I acknowledge that Springboot workflows are not my strong suit. :)
Sure thing! I'll contact you whenever I'll have a chance to look at the issue more deeply. Right now, I managed to make it work.
The problem was with the postgred:offline URL I provided. It used to work, but now it doesn't anymore. I replaced the url with my local postgresql database and it sorta work.
I wouldn't be surprised if my work flow was not correct at all 😄
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi Damien,
I believe it maybe the name of the output file has to include the type of database platform. Could you try changing migration.sql to migration.postgresql.sql
Also, you can get help on our forum (I just randomly checked here, usually don't search dev.to for liquibase issues):
forum.liquibase.org/
or real-time (ish) chat on our Discord channel:
discord.gg/9yBwMtj
Detailed instructions for generatechangelog, maybe it is the same for updatesql:
Running the generatechangelog command
liquibase --changeLogFile=dbchangelog.xml generateChangeLog
Note: For the SQL changelogs, you need to specify the database type in the file name. The command should be the following:
liquibase --changeLogFile=dbchangelog..sql generateChangeLog
Replace with the short name of the targeted database type. These include h2, oracle, postgresql, and mysql.
The generateChangeLog command generates a changelog that contains your objects (represented as changesets) and places the file in the same directory where the command was run.
Hope that helps!
Ronak
Thank you Ronak, I'll take a look!
Hah! I hope it works. Once this gets resolved, I would like to understand a little more why your workflow is this way. My users typically just run a liquibase update rather than translate to sql into a file but I acknowledge that Springboot workflows are not my strong suit. :)
Sure thing! I'll contact you whenever I'll have a chance to look at the issue more deeply. Right now, I managed to make it work.
The problem was with the postgred:offline URL I provided. It used to work, but now it doesn't anymore. I replaced the url with my local postgresql database and it sorta work.
I wouldn't be surprised if my work flow was not correct at all 😄