jpa.ddl defaults to update though commented out
Bug #544536 reported by
Robert Toellner
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| play framework |
Fix Committed
|
Undecided
|
Unassigned | ||
| 1.0 |
Won't Fix
|
Undecided
|
Unassigned | ||
| 1.1 |
Fix Committed
|
Undecided
|
Unassigned | ||
Bug Description
Even though the jpa.ddl setting is commented out in application.conf to begin with - it defaults to update. Anyone unsuspecting and using an existing database to test against ( i.e. to prototype a new Play app against an existing db and schema ) can have their tables modified unwanted and unaware. Would suggest to default to jpa.ddl=none and force users to uncomment the entry to have ddl updates maintained. Perhaps also, a production check to ensure a move to prod forces a user to manually make an additional or prod specific change and help prevent any accidental ddl changes to the db.
| security vulnerability: | yes → no |
| visibility: | private → public |
Revision history for this message
| Guillaume Bort (guillaume-bort) wrote | #1 |
| Changed in play: | |
| status: | New → Fix Committed |
To post a comment you must log in.
Default to 'none' in PROD mode.