What happens internally when you run "gradlew cleanAll loadAll"?

cleanAll and loadAll are two separate Gradle tasks usually run together during setup or a full reset:

1. cleanAll drops and recreates the configured database schema(s), wiping all existing data, based on every component's merged entitymodel.xml.
2. loadAll then reloads XML data files across all installed components, typically in this order: seed data first (core reference/status values everything depends on), then seed-initial (first-run setup data like the default admin user), then demo data (sample products, parties, and orders) if present.

Because the Entity Engine derives the schema fresh from the current entitymodel.xml definitions each time, this combination is also the standard way to pick up newly added entities or fields during development, rather than hand-writing an ALTER TABLE statement.

Running this against a real production database is destructive, so it's normally reserved for local development and demo environments only.