You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a new table SchemaVersion or something is used with a single integer being the current database layout then a new release can bump the expected version if there were database changes. Then FileSender can warn the sys admin that the database upgrade script must be run to complete the update instead of relying on people remembering/checking this for each time.
The text was updated successfully, but these errors were encountered:
To allow major database migrations there is now the https://github.com/filesender/filesender/blob/master/classes/data/Metadata.class.php table. I think it is useful to expect the update script to be run to handle minor updates, if there is nothing to update then it should return fairly quickly. With versioning for minor updates there is always the possibility of forgetting to bump the minor version and admins expecting the system to complain only when the update script must be run. If the expectation is to check the later then smaller changes will automatically be handled.
If a new table SchemaVersion or something is used with a single integer being the current database layout then a new release can bump the expected version if there were database changes. Then FileSender can warn the sys admin that the database upgrade script must be run to complete the update instead of relying on people remembering/checking this for each time.
The text was updated successfully, but these errors were encountered: