Problem with database diffing tool in 3.4.x

Author Message

Timmothy Green

Friday 15 April 2005 7:13:25 am

I have upgraded from 3.3-4 to 3.4.4 following the upgrade path. My 3.4.4 installation appears to be stable and I'd like to move on to 3.5, however, when I run the Check Database under System Upgrade or use the ezsqldiff script it tells me to run these sql commands:

ALTER TABLE ezdiscountsubrule CHANGE COLUMN limitation limitation char(1) DEFAULT NULL ;
ALTER TABLE ezrole CHANGE COLUMN value value char(1) DEFAULT NULL ;

I have run those commands, yet the diffing tool still gives the same results.

I have created a new database and imported the kernel_schema.sql and cleandata.sql scripts from kernel/sql/mysql. When I compare that database to mine it says the schemas are identical.

Sorry, if I'm rehashing an old topic. I thought I had seen somewhere in the eZ community that this was a known issue, but over the last two days I haven't been able to find it with any searches.

Automation Technologies, Inc.
http://www.ati4it.com

Frederik Holljen

Monday 18 April 2005 5:09:43 am

The behavior is probably due to a small bug in the database diff tool. Please create a bug report on the issue.
It should be safe for you to perform the upgrade.

Timmothy Green

Monday 18 April 2005 6:23:27 am

Thanks,

I've opened a bug report as requested.

http://www.ez.no/bugs/view/6495

Automation Technologies, Inc.
http://www.ati4it.com

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.