- created a customer.jdl with two fields
- generated code using jhipster import-jdl customer.jdl.
- Built the generated code, ensured potgres server up and running and the configured db is created
- Upon running the service it applied (for eg 20240612174911_added_entity_Customer.xml). This resulted in the table creation
- Now I added another field to jdl and followed steps starting step 2 above.
- Code is updated to accomodate the new column. However it adds to the same file 20240612174911_added_entity_Customer.xml the new column. Isn’t this voilation of the liquibase design principle of nt to modify ones the changeset is created. A new xml should have been generated to add this new column def right?
- When I run the ervice with abovve generated code i end up seeing same error.
I see JHipster is adding to the already generated changeset which is voilating the liquibase principle of not changing ones generated changeset. Since its doing that its failing by itself as it tries apply the same xml but with added column as its checksum changes
I want know is it a limitation in JHipster? Is there a solution? This is very common acenario and I hope JHipster being a professional tool should have handled
Tried all steps and double checked i my system
New contributor
J D R is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.