On Apr 24, 2015, at 15:10 , Thomas, Gregory A <thom...@uwp.edu> wrote:
> I can not be 100% sure that I did both sql updates when I moved point
> versions, but I am sure that something would have broken had I not. As said
> on a thread with this upgrade, it would be nice if the sql update was
> included as part of the updating package as that is something that is easily
> overlooked and can/will cause problems down the upgrade path.
You may be interested in knowing that that is something we are working on.
At the moment database schema changes cannot be done automatically because the
package cannot know which version (of the schema) it is starting from.
We are working on adding an internal log of all schema versions so that we can
see what is the current one and apply only the missing changes from it.
That would have the added benefit of making it easy to see if you skipped a
schema change between two releases.
We aim to get that working in 5.1, due out in about a month.
Regards,
--
Louis Munro
lmu...@inverse.ca :: www.inverse.ca
+1.514.447.4918 x125 :: +1 (866) 353-6153 x125
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
(www.packetfence.org)
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users
