Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #32432 All Revisions ] Back to Issue ]
Summary 0032432: incorrect dates issue detection on install.source
Revision 2016-03-08 08:52 by alostale
Description Previous PostrgreSQL jdbc had an issue with dates when not using Tomcat pool which was fixed by issue 0031959.

The fix included a module script to detect instances in this situation. This script is executed on install.source incorrectly flagging the instance as being affected by this issue.

This problem affects instances that:
* Do no use Tomcat connection pool
* Are in a pi version between 15Q4 and 16Q1

Note instances in this situation will be flagged as potentially problematic also after this is fixed when they are updated to some version previous to 16Q1 because the script uses core's version number which is pi revision number at the time the issue was fixed +1, as 16Q1 has not been published yet, and version number has not been increased there is no way to properly detect this case.
Revision 2016-03-08 08:37 by alostale
Description Previous PostrgreSQL jdbc had an issue with dates when not using Tomcat pool which was fixed by issue 0031959.

The fix included a module script to detect instances in this situation. This script is executed on install.source incorrectly flagging the instance as being affected by this issue.

This problem affects instances that:
* Do no use Tomcat connection pool
* Are in a pi version between 15Q4 and 16Q1


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker