Postgresql 8.X and reservation agenda
Bug #553373 reported by
max-csa
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| bureauvirtuel |
New
|
Undecided
|
Unassigned | ||
Bug Description
When using Postgresql JAR file version 8.X, conflicts in reservation agendas are not computed correctly and allow to book a ressource twice for the same timeframe.
It seems that Torque is related to this bug since this librairy is used to caculate conflicts.
However, if we use Postgresql JAR file version 7.4, everything works well, but using JAR file version 7.4 with a server version 8.X in a production environment is not recommended.
Revision history for this message
| max-csa (max-csa) wrote | #1 |
To post a comment you must log in.
The version of Torque currently used with the BV is 3.1.
After upgrading Torque to 3.3, as well as all other dependant librairies, the result got worse. No event at all were displayed in any kind of agenda. So something needs to be done to get the agenda work with Torque 3.3