ibank-sql-pack

Generate deterministic SQL seed data for iBank by producing ready-to-run insert statements for dummy users, teams, staffing, and worklogs from approved drafts, enforcing stable IDs and reusing a shared BCrypt hash across records.

SQL seed data generation maintains table dependencies by respecting insert order across tb_user, tb_team, tb_team_admin, tb_user_team, tb_worklog, tb_worklog_dependency, and tb_worklog_status_history to preserve relational integrity.

You can generate SQL seed inserts for multiple related database tables in a single run, producing deterministic, insert-ready SQL files that preserve existing approved drafts while maintaining dependency order.

You need approved drafts or generated content to generate final SQL seed data for iBank tables, because the process preserves existing drafts and outputs ready-to-run insert files derived from those already-decided records.

The best way to populate tb_user and tb_team with dummy seed data is to generate final SQL insert files that enforce stable IDs, reuse a shared BCrypt hash, and maintain insert order for related tables.

SQL seed data generation preserves existing drafts for tb_worklog by deriving final insert statements from already-decided content; if drafts are overwritten, ensure the input workflow provides approved generated content before execution.