Report Extension - Migrate between versions?
-
Our current setup is with Postgres db and AWS blob storage (saved for 30days). If the update to jsreport requires us to create a new schema in the database all references to the reports in our AWS are now lost.
And we run into two issues..- The client no longer has access to this report and will need to regenerate it. Which is problematic as we send out emails with links to these reports some times.
- The report will now need be cleaned up manually due to Jsreport no longer knowing it exists.
Is there a way to migrate these references between schemas when we do this?
-
I see.
The jsreport is very stable and mature, and the schema changes are minimal these days.
I will recommend running schema alters manually instead of recreating schemas.
We will start adding the changes to the release notes, so you know what to alter.
If you are interested in a specific update now, I can find the schema changes in the git log.
-
Thanks that should work for us.
Can we get the schema changes between 4.7 and 4.8 as well as 4.8 and 4.9 if there are any?
-
4.7 -> 4.8
added column jsreport_ReportType.meta as string4.8 -> 4.9
none
-
Yes, a manual update should work for us this time. For the future, even though schema changes will likely be rare, would it be possible to automate the process so we can avoid manual upgrade steps?
-
@apanin-locusview It is in the backlog, but with a lower priority than other things we are currently working on.