Pull request #410: db liquibase changes for h2

Merge in WALTZ/waltz from ~ABHIJIT.JEJURKAR_DB.COM/waltz-aj:CTCTOWALTZ-3392-ddl-change-7162 to db-feature/waltz-7162-add-table-comment-change-log

* commit 'ebbea8c9b2f39119f3f1234e2d3b055a8d2c835d':
  db liquibase changes for h2

waltz-schema/src/main/resources/liquibase/db.changelog-1.65.xml

@@ -56,67 +56,78 @@
                           tableName="user_agent_info"/>
     </changeSet>
     <changeSet id="20241009-7162-6"
-               author="jejuabh">
+               author="jejuabh"
+               dbms="!h2">
         <comment>7162: Add description to table qrtz_triggers</comment>
         <setTableRemarks  remarks="is where general information of a trigger is saved"
                           tableName="qrtz_triggers"/>
     </changeSet>
     <changeSet id="20241009-7162-7"
-               author="jejuabh">
+               author="jejuabh"
+               dbms="!h2">
         <comment>7162: Add description to table qrtz_simprop_triggers</comment>
         <setTableRemarks  remarks="have a foreign key relation to qrtz_triggers which save those specific details. Ex. Cron has cron expression which is unique to it."
                           tableName="qrtz_simprop_triggers"/>
     </changeSet>
     <changeSet id="20241009-7162-8"
-               author="jejuabh">
+               author="jejuabh"
+               dbms="!h2">
         <comment>7162: Add description to table qrtz_simple_triggers</comment>
         <setTableRemarks  remarks="have a foreign key relation to qrtz_triggers which save those specific details. Ex. Cron has cron expression which is unique to it."
                           tableName="qrtz_simple_triggers"/>
     </changeSet>
     <changeSet id="20241009-7162-9"
-               author="jejuabh">
+               author="jejuabh"
+               dbms="!h2">
         <comment>7162: Add description to table qrtz_scheduler_state</comment>
         <setTableRemarks  remarks="is for capturing the node state so that if in any case one node gets down or failed to execute one of the job then the other instance running in clustering mode can pick the misfired job"
                           tableName="qrtz_scheduler_state"/>
     </changeSet>
     <changeSet id="20241009-7162-10"
-               author="jejuabh">
+               author="jejuabh"
+               dbms="!h2">
         <comment>7162: Add description to table qrtz_paused_trigger_grps</comment>
         <setTableRemarks  remarks="is to save the information about triggers which are not active"
                           tableName="qrtz_paused_trigger_grps"/>
     </changeSet>
     <changeSet id="20241009-7162-11"
-               author="jejuabh">
+               author="jejuabh"
+               dbms="!h2">
         <comment>7162: Add description to table qrtz_locks</comment>
         <setTableRemarks  remarks="stores the value of the instance name executing the job, to avoid the sceanario of multiple nodes executing the same job"
                           tableName="qrtz_locks"/>
     </changeSet>
     <changeSet id="20241009-7162-12"
-               author="jejuabh">
+               author="jejuabh"
+               dbms="!h2">
         <comment>7162: Add description to table qrtz_job_details</comment>
         <setTableRemarks  remarks="the task to be executed."
                           tableName="qrtz_job_details"/>
     </changeSet>
     <changeSet id="20241009-7162-13"
-               author="jejuabh">
+               author="jejuabh"
+               dbms="!h2">
         <comment>7162: Add description to table qrtz_fired_triggers</comment>
         <setTableRemarks  remarks="is a log of all the triggers that were fired."
                           tableName="qrtz_fired_triggers"/>
     </changeSet>
     <changeSet id="20241009-7162-14"
-               author="jejuabh">
+               author="jejuabh"
+               dbms="!h2">
         <comment>7162: Add description to table qrtz_cron_triggers</comment>
         <setTableRemarks  remarks="have a foreign key relation to qrtz_triggers which save those specific details. Ex. Cron has cron expression which is unique to it."
                           tableName="qrtz_cron_triggers"/>
     </changeSet>
     <changeSet id="20241009-7162-15"
-               author="jejuabh">
+               author="jejuabh"
+               dbms="!h2">
         <comment>7162: Add description to table qrtz_calendars</comment>
         <setTableRemarks  remarks="for excluding blocks of time from the the trigger’s firing schedule. For instance, you could create a trigger that fires a job every weekday at 9:30 am, but then add a Calendar that excludes all of the business’s holidays"
                           tableName="qrtz_calendars"/>
     </changeSet>
     <changeSet id="20241009-7162-16"
-               author="jejuabh">
+               author="jejuabh"
+               dbms="!h2">
         <comment>7162: Add description to table qrtz_blob_triggers</comment>
         <setTableRemarks  remarks="for excluding blocks of time from the the trigger’s firing schedule. For instance, you could create a trigger that fires a job every weekday at 9:30 am, but then add a Calendar that excludes all of the business’s holidays"
                           tableName="qrtz_blob_triggers"/>