view_access.ctime NULL/NOT-NULL is different on upgrade (from 1.3) or clean install
Bug #1494128 reported by
Aaron Wells
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mahara |
Won't Fix
|
Medium
|
Unassigned | ||
Bug Description
As reported on the forums: https:/
The view_access.ctime column was added in this commit: https:/
The upgrade script for that commit creates it as a NULLable column, while the install.xml for it creates it as a NOT NULL column.
So this results in some schema drift for sites that were created prior to Mahara 1.4. There may also be a bug caused during 1.8.1 to 15.04.3 upgrades, due to this.
| Changed in mahara: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| Changed in mahara: | |
| assignee: | nobody → Robert Lyon (robertl-9) |
Revision history for this message
| Robert Lyon (robertl-9) wrote | #1 |
| Changed in mahara: | |
| status: | Confirmed → Won't Fix |
| assignee: | Robert Lyon (robertl-9) → nobody |
To post a comment you must log in.
This is too old a bug to fix auto-magically
If a site is needing to upgrade from pre 1.4 to something more modern they will need to later the database pre-upgrade to:
1) Make sure all view_access rules are not null (they can use the view mtime as a logic ctime for this)
2) Make the view_access table ctime column to be a not-null column