Monica-CodingWorld commented on code in PR #5264:
URL: https://github.com/apache/fineract/pull/5264#discussion_r2688549401


##########
fineract-provider/src/main/resources/db/changelog/tenant/parts/0072_add_result_and_status_to_command_source.xml:
##########
@@ -24,19 +24,22 @@
                    
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog 
http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-4.1.xsd";>
 
     <changeSet id="1" author="fineract" context="postgresql">
+        <validCheckSum>9:b1a2065c6c2f9fba5035e700435a80ab</validCheckSum>
         <renameColumn newColumnName="status"
                        oldColumnName="processing_result_enum"
                        tableName="m_portfolio_command_source"/>
     </changeSet>
 
     <changeSet id="2" author="fineract" context="mysql">
+        <validCheckSum>9:9c4456b507915a0ee7a16edca4cddb46</validCheckSum>

Review Comment:
   The `validCheckSum` is needed because Liquibase generates checksums for each 
changeset based on the file content. When there was a space in the filename, 
Liquibase couldn't properly validate the changeset checksums.
   Adding explicit `validCheckSum` elements:
   1. Provides known-good checksums that Liquibase can validate against
   2. Prevents "Invalid checksum" errors during database updates
   3. Ensures consistent behavior across different environments
   
   These checksums were generated from the corrected (space-removed) version of 
the file.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to