Feature request: support Liquibase integration

[sheltonsuen]

Is your feature request related to a problem? Please describe.

Yes, when we trying to do some automation using tools like: liquibase, we encountered some issue related to getSQLKeywords from metadata

1. normal postgresql will return keywords

2. risingwave just return null

Describe the solution you'd like

e... as far as I know, maybe we should support this by return the kewords that we reserved

Describe alternatives you've considered

Not yet

Additional context

The automation pipeline we trying to build is just a database migration, so that we can keep multi envs consitent with each other, and even do some sql interpolations

[sheltonsuen]

maybe db migration is not the ideal way to do automation, any suggestions welcome

[xxchan]

maybe db migration is not the ideal way to do automation, any suggestions welcome

May I ask what kind of automation do you want? 👀

[sheltonsuen]

CI/CD from my perspective, currently, we have multi envirements: dev, uat,..., prod
And we want the sql scripts been deployed to different envirements once the code push to the remote

workflow may like : lcoal repo -> gitlab -> pipeline -> dev (automatic) -> uat(mannual) -> prod( mannual)
so the liquibase like tools will help us sync sql scripts

[neverchanje]

Thanks for sharing the use case. We'll need some time to investigate if Postgres's liquibase integration can aslo work on RisingWave.

By the way, we also support Bytebase, although the integration doc is still on the way. AFAIK it's kinda like a Liquidbase alternative.

[sheltonsuen]

Bytebase are too complicated and encapsulated, Liquidbase like tools are more pure

[github-actions]

This issue has been open for 60 days with no activity. Could you please update the status? Feel free to continue discussion or close as not planned.

[github-actions]

This issue has been open for 60 days with no activity. Could you please update the status? Feel free to continue discussion or close as not planned.