Hi ,
we are evaluating liquibase within our team and we have notice an issue more like a glitch when we issue the command to get the information on what has been deployed within the atabase schema : **lb history**
it does not matter the type of the changeset of the number the pattern can be reproduce every time ( currently using version SQLcl: Release 24.3 )
What happens is that when we issue the first time the command we have for instance :
LIQUIBASE_POC@//sthoradeve.space.gc.ca:1535/CORPDEVE SQL>lb history
--Starting Liquibase at 2024-12-13T10:11:54.852301900 (version 4.25.0.305.0400 #0 built at 2024-10-31 21:25+0000)
Liquibase History for jdbc:oracle:thin:@//sthoradeve.space.gc.ca:1535/CORPDEVE
- Database updated at 12/13/24, 10:11ÔÇ»AM. Applied 2 changeset(s) in 0.564s, DeploymentId: 4102686143
debug/print_output.xml::abcd1234567890::Generated
debug/print_output_2.xml::abcd1234567890::Generated
without doing anything else when we run the second time we have :
LIQUIBASE_POC@//sthoradeve.space.gc.ca:1535/CORPDEVE SQL>lb history
--Starting Liquibase at 2024-12-13T10:14:56.592848800 (version 4.25.0.305.0400 #0 built at 2024-10-31 21:25+0000)
Liquibase History for jdbc:oracle:thin:@//sthoradeve.space.gc.ca:1535/CORPDEVE
- Database updated at 12/13/24, 10:11ÔÇ»AM. Applied 4 changeset(s) in 0.564s, DeploymentId: 4102686143
debug/print_output.xml::abcd1234567890::Generated
debug/print_output_2.xml::abcd1234567890::Generated
debug/print_output.xml::abcd1234567890::Generated
debug/print_output_2.xml::abcd1234567890::Generated
without doing anything else when we run the third time we have :
LIQUIBASE_POC@//sthoradeve.space.gc.ca:1535/CORPDEVE SQL>lb history
--Starting Liquibase at 2024-12-13T10:22:41.154339900 (version 4.25.0.305.0400 #0 built at 2024-10-31 21:25+0000)
Liquibase History for jdbc:oracle:thin:@//sthoradeve.space.gc.ca:1535/CORPDEVE
- Database updated at 12/13/24, 10:11ÔÇ»AM. Applied 6 changeset(s) in 0.564s, DeploymentId: 4102686143
debug/print_output.xml::abcd1234567890::Generated
debug/print_output_2.xml::abcd1234567890::Generated
debug/print_output.xml::abcd1234567890::Generated
debug/print_output_2.xml::abcd1234567890::Generated
debug/print_output.xml::abcd1234567890::Generated
debug/print_output_2.xml::abcd1234567890::Generated
As you can see the two changeset applied are added to the liquibase history over and over everytime we issue the command liquibase history.
Note that when we close the session and reconnect the lb history is back ok the first time we run it but when we issue the command again it will duplicate the information
Note also that within the table databasechangelog we have the finromation ok.
So not really an error more like a glitch .
Thank you.