-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop support for sqlplus, sqlcl Liquibase ci/cd #63
Comments
sorry, I need sqlplus, because we are still working with Oracle 11 in our company. I guess, I'm not the only one. |
mmm ok, we will have to limit some features only if you have installed sqlcl. |
Yes, no problem, I think that SqlCl is set to execute by default, so no problem if some features don't work if you switch to sqlplus. |
hej! Latest version of sqlcl has some additional liquibase fatures... https://www.thatjeffsmith.com/archive/2021/10/versions-21-3-of-sqlcl-ords-sqldev-web-now-available/ |
Wow very interesting, I was waiting for this as standard Liquibase has support for this. I will try to have a look at it. We might even replace curent schema sql generator with sqlcl generator. I found it quite slow generating changelogs, it might have improved. I will have a look at this. |
SQLcl Liquibase file structure is a bit different than oradew project structure, what do you thing about renaming some of the object type's to liquibase ones? (Liquibase -> Current in oradew) apex -> APEX |
I will just create two new command, like import liquibase and deploy liquibase for keeping current compatibility. |
We already use a mapping for object types, I think we can extend it or create sth similar for luqibase: oradew-vscode/src/cli/common/dbobject.ts Lines 57 to 78 in 6372784
oradew-vscode/src/cli/common/dbobject.ts Lines 140 to 141 in 6372784
... oradew-vscode/src/cli/common/dbobject.ts Line 211 in 6372784
|
What do you think about dropping support for sqlplus? I say it because I plan to add sqlcl liquibase ci/cd compatibility in liquibase, and for me I don't see any advantages of mantaining two different implementations as sqlcl can do everything and more than sqlplus can do.
The text was updated successfully, but these errors were encountered: