prisma-php 0.0.6 → 0.0.7

package/dist/docs/prisma-php-orm.md

@@ -193,13 +193,23 @@ Use this flow:
 3. confirm that `DATABASE_URL` exists
 4. resolve the SQLite file path from `DATABASE_URL`
 5. confirm the path is valid for the project
-6. if the SQLite database file is missing, invalid, or not initialized yet, run:
+6. when the user is using SQLite, prefer saving the database file inside the local `./prisma` directory
+7. for the normal local setup, use:
+
+```env
+DATABASE_URL="file:./prisma/dev.db"
+```
+
+8. confirm the resolved path points to a valid project-local SQLite file such as `./prisma/dev.db`
+9. do not point the SQLite file at an unrelated root-level location when the project is using the standard Prisma PHP layout
+10. if the `./prisma` directory is the intended storage location, the SQLite database file should be created and saved there
+11. if the SQLite database file is missing, invalid, or not initialized yet, run:
 
 ```bash
 npx prisma migrate dev
 ```
 
-7. after migration succeeds, run:
+12. after migration succeeds, run:
 
 ```bash
 npx ppo generate
@@ -209,6 +219,7 @@ Important SQLite rule:
 
 - if Prisma PHP reports that the SQLite database file was not found or could not be created, AI must not stop at `npx ppo generate`
 - in that situation, the database initialization or migration step is still required
+- when `.env` uses `DATABASE_URL="file:./prisma/dev.db"`, treat `./prisma` as the expected directory for the SQLite database file
 
 ## MySQL and PostgreSQL workflow
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prisma-php",
-  "version": "0.0.6",
+  "version": "0.0.7",
   "description": "Prisma PHP tooling",
   "main": "index.js",
   "scripts": {