Search found 4 matches
- 15 Sep 2010, 15:16
- Forum: Help
- Topic: why was all the datetime fields switched to int without migr
- Replies: 1
- Views: 1925
why was all the datetime fields switched to int without migr
my question is why was the datetime field changed to int and the data wasn't migrated? I upgraded from 1.1.8 to 1.2.3 and had to run the database scripts manually. After the upgrade all the last updated fields are 1969-12-31. Why would you create the new field, drop the old constraints and field ...
- 14 Sep 2010, 16:17
- Forum: Help
- Topic: Upgrade from 1.1.8 to 1.2.2 not so good
- Replies: 6
- Views: 10575
Re: Upgrade from 1.1.8 to 1.2.2 not so good
Still doesn't explain why my install isn't detecting that it's an upgrade during the db script part. It's still trying to do a create on the tables.
- 01 Sep 2010, 19:22
- Forum: Help
- Topic: Upgrade from 1.1.8 to 1.2.2 not so good
- Replies: 6
- Views: 10575
Re: Upgrade from 1.1.8 to 1.2.2 not so good
[ Back to Administration ] Pre-Installation Check
APPLICATION WARNING #403: Database field "enabled" not found.
Checking Installation...
Config File Exists - Upgrade GOOD
Setting Database Type GOOD
Checking Database connection settings exist GOOD
Checking PHP support for database type GOOD
Config ...
APPLICATION WARNING #403: Database field "enabled" not found.
Checking Installation...
Config File Exists - Upgrade GOOD
Setting Database Type GOOD
Checking Database connection settings exist GOOD
Checking PHP support for database type GOOD
Config ...
- 01 Sep 2010, 15:37
- Forum: Help
- Topic: Upgrade from 1.1.8 to 1.2.2 not so good
- Replies: 6
- Views: 10575
Upgrade from 1.1.8 to 1.2.2 not so good
Couple of observations. The Database_version field in the config file was not there from the 1.1.8 version. Therefore the install.php would think it's a new installation. I set it to $g_database_version = '1.1.8'; and it doesn't show the bad config file anymore. This being said, it's still trying to ...