Date problem

[guillaume.renaudin@…]

When setting a date within Trac I get the 'integer out of range' message as long as the date specified is greater than '01/01/70 01:35:47'.

[Christian Boos]

This is an InstallationIssue. You have done an upgrade which has failed, at least partially and now you have a "mixed state": the code is using [TracDev/ApiChanges/0.12#Timestampstorageindatabase microsecond timestamps] (as it should in 0.12), but your database is still expecting seconds timestamps.

Restart from your 0.11 backup, try to update again and if it fails again, report that error.

Or the problem happens only within a plugin which has not been upgraded. Hard to tell without a traceback.

[anonymous]

We fixed the problem by changing the type of 'due' and 'completed' columns of the milestone table to bigint. Setting due or completed dates now works fine

[Christian Boos]

Thanks for the feedback!

But this conversion should have happened during the upgrade, see source:tags/trac-0.12.3/trac/upgrades/db25.py​. You should verify that all the relevant fields are OK.

[anonymous]

Well in fact we did not upgrade but installed v0.12 from scratch. And the problem was there. Best regards.

Replying to cboos:

Thanks for the feedback!

But this conversion should have happened during the upgrade, see source:tags/trac-0.12.3/trac/upgrades/db25.py​. You should verify that all the relevant fields are OK.

[Christian Boos]

Replying to anonymous:

Well in fact we did not upgrade but installed v0.12 from scratch. And the problem was there.

This is most surprising, see tags/trac-0.12/trac/db_default.py#L151​, i.e. the use of long integers was specified right there from 0.12.0 (you even mention a version of 0.12.3).

Which database are you using, which version? Same questions for the Python bindings to the database client library.