Can one have a project with a relational database that is deployed early and often, and not have thousands of SQL migration scripts? Seems like it’s difficult to have both. Maybe there’s some way to “roll up” old migration scripts into one nice SQL schema. I guess running them all on a new database and exporting the schema will do that. 🤔

Prisma provides a "baseline" to reset merge all migration scripts. There are always many migrations though.

In December, the company suffered a breach where attackers gained unauthorized access to one of its customer support portals, PowerSource, and stole sensitive data from 6,505 school districts.

The stolen data includes varying types of information per district, including full names, physical addresses, contact information, Social Security numbers (SSNs), medical data, and grades.