docs: clarify migration instructions and add note on ClickHouse unique constraints

NoOne7135 · NoOne7135 · commit 5a5cc98b2558 · 2026-06-05T15:25:40.000+03:00
diff --git a/adminforth/commands/createApp/templates/readme.md.hbs b/adminforth/commands/createApp/templates/readme.md.hbs
@@ -15,9 +15,10 @@ The generated app will seed the default `adminforth` / `adminforth` user on firs
 {{/if}}
 
 {{#if prismaDbUrl}}
-Migrate the database:
+Create the initial migration and apply it to the database:
 
 ```bash
+{{packageManagerRun}} makemigration{{packageManagerScriptArgSeparator}}--name init
 {{packageManagerRun}} migrate:local
 ```
 {{/if}}
diff --git a/adminforth/commands/createApp/utils.js b/adminforth/commands/createApp/utils.js
@@ -111,7 +111,9 @@ CREATE TABLE adminuser (
 )
 ENGINE = MergeTree()
 ORDER BY id;
-\`\`\``;
+\`\`\`
+
+ClickHouse does not enforce UNIQUE constraints like PostgreSQL, MySQL, or SQLite. AdminForth authentication expects `email` values in `adminuser` to be unique, so enforce this in your ingestion/application logic and remove duplicate email rows to avoid ambiguous logins.`;
   }
 
   if (provider === 'mongodb') {

Original file line number	Diff line number	Diff line change
`@@ -111,7 +111,9 @@ CREATE TABLE adminuser (`
`111`	`111`	`)`
`112`	`112`	`ENGINE = MergeTree()`
`113`	`113`	`ORDER BY id;`
`114`		-\`\`\``;
	`114`	+\`\`\`
	`115`	`+`
	`116`	+ClickHouse does not enforce UNIQUE constraints like PostgreSQL, MySQL, or SQLite. AdminForth authentication expects `email` values in `adminuser` to be unique, so enforce this in your ingestion/application logic and remove duplicate email rows to avoid ambiguous logins.`;
`115`	`117`	`}`
`116`	`118`
`117`	`119`	`if (provider === 'mongodb') {`