[
https://issues.apache.org/jira/browse/FINERACT-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18106400#comment-18106400
]
Sonigra Bhavya Hemendrabhai edited comment on FINERACT-2704 at 8/20/26 6:40 PM:
--------------------------------------------------------------------------------
Haha, thanks [~meonkeys]! Honestly, my DB fundamentals are pretty solid since
I'm finishing up my CS undergrad, but I mostly used AI as a sounding board to
map out the schema and build a game plan before touching anything.
At first, I thought it was going to be a straightforward script, but after
spending a solid two hours just sketching out the migration edges, your "good
luck!" comment flashed in my head.
Nerves are definitely hitting a bit since this is a massive PR and only my 4th
one overall, but I'm super stoked with how clean it turned out.
To answer your workflow question: I didn't rely solely on AI agents I mostly
used them to understand complex concepts and find flaws in my own decisions.
Apart from that, I used Gemini to help parse and convert data blocks into SQL
files, Claude for reasoning through the tricky architectural decisions and
sequence resets, and a mix of other tools for local testing and minor fixes.
I hope this will help you \:D
was (Author: JIRAUSER314311):
Haha, thanks [~meonkeys]! Honestly, my DB fundamentals are pretty solid since
I'm finishing up my CS undergrad, but I mostly used AI as a sounding board to
map out the schema and build a game plan before touching anything.
At first, I thought it was going to be a straightforward script, but after
spending a solid two hours just sketching out the migration edges, your "good
luck!" comment flashed in my head.
Nerves are definitely hitting a bit since this is a massive PR and only my 4th
one overall, but I'm super stoked with how clean it turned out.
To answer your workflow question: I didn't rely solely on AI agents I mostly
used them to understand complex concepts and find flaws in my own decisions.
Apart from that, I used Gemini to help parse and convert data blocks into SQL
files, Claude for reasoning through the tricky architectural decisions and
sequence resets, and a mix of other tools for local testing and minor fixes.
I hope this will help you :D
> re-baseline database migrations
> -------------------------------
>
> Key: FINERACT-2704
> URL: https://issues.apache.org/jira/browse/FINERACT-2704
> Project: Apache Fineract
> Issue Type: Improvement
> Components: Build
> Reporter: Adam Monsen
> Priority: Minor
> Labels: beginner
> Attachments: Screenshot 2026-08-20 at 11.18.23 PM.png
>
>
> {{./gradlew devRun}} is pretty slow for a fresh database. Part of the reason
> is that many liquibase database migrations need to run.
> Re-baseline our db migrations as of the current release (1.15.0): create an
> empty database, run all migrations, then re-create initial schema and initial
> data files. Leave any schema/data migrations created post-1.15.0 in place,
> but you may re-number all initial and migration files starting at 0001.
> We'll plan on doing this once per release, back to the last supported/stable
> release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
