[#12578] - [4.0] Refactor Schema Validation and Management
- Closed
- 3 Apr 2018
- Medium
- Build: master
- # 12578
The JSchemaChange* API and its schema validation right now relies on the update SQL files to ensure the database is in an expected state. This API cannot work with a base SQL file which should have the full schema (for an extension this would be their install.sql type files, for core this would be joomla.sql).
Core cannot use joomla.sql for validation because it mixes data and schema, and this SQL lives only in the installation directory so it is not persistent on a site.
Therefore, I propose several things if someone can find time and interest:
- Splitting
joomla.sqlinto the base schema itself and data statements - Moving the schema only version of
joomla.sqlto a location that persists on a site - Improving the schema validation API to be able to take into consideration a base schema file in addition to change deltas as a means for validating the schema is in an expected state
brianteeman
- | Category | ⇒ | Libraries |
zero-24
- | Labels |
Added:
?
|
||
| Milestone |
Added: |
||
| Labels |
Removed:
?
|
||
joomla-cms-bot
- | Title |
|
||||||
franz-wohlkoenig
- | Title |
|
||||||
| Status | New | ⇒ | Needs Review | ||||
| Title |
|
||||||
| Labels |
Added:
?
|
||
| Labels |
Added:
J4 Issue
|
||
Already spending too much time on prepared statement on my own, not interested in adding more database tooling in my workload and don't see much interest otherwise.
| Status | Needs Review | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-04-03 12:31:11 |
| Closed_By | ⇒ | mbabker |
sorry for not demonstrating interest before now, but this goes out of my radar till now like many others i'm afraid
but yes, it seems like 4 is only focused on frontend stuff no one cares about schema/db's and backend stuffs
Propose moving the joomla db schema part to
/administrator/components/com_admin/install/<dbdriver>/schema.sql