1 ben_merrill Sep 18, 2007 22:33
3 ben_merrill Sep 28, 2007 17:24
This issue was solved by first upgrading to 2.0.0 Alpha, and then to 2.0.1 Alpha in turn. This is odd, however, because the update from 2.0.0 Alpha to 2.0.1 Alpha did not require any database modification. Therefore, there must be a difference between the database updater for 2.0.1 Alpha, and that of 2.0.0 Alpha. Either way, I'm looking forward to 2.0.2. Any hints on when it is coming our way?
I have recently run a 1.10.2 to 2.0.2 upgrade and did not stumble onto this.
Sure there's been some fixes in 2.0.2 already but none of them involved the sessions table as far as I recall.
This is odd.