Share » Forums » Developer » DB errors when upgrading to 3.10.1.rc1

DB errors when upgrading to 3.10.1.rc1

DB errors when upgrading to 3.10.1.rc1

Thursday 17 July 2008 6:12:24 am - 2 replies

Author Message

André R.

Thursday 17 July 2008 11:23:45 am

There should be a script included to fix that, anyway you can download it here if it wasn't included in rc:
http://pubsvn.ez.no/nextgen/stable/3.10/update/common/scripts/3.10/fixobjectremoteid.php

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

Andrew Kelly

Friday 18 July 2008 2:59:11 am

Thanks André, much appreciated. Maybe there should be a brief note to that effect in the documentation?

Sadly, like much of the scripting available, this one also seems to be built only for MySQL and fails without any kind of helpful information when used on a PostgreSQL installation.

This line:

SELECT remote_id, COUNT(*) cnt FROM ezcontentobject GROUP BY remote_id HAVING cnt > 1;

won't even successfully complete from the command line (psql), and should be changed to

SELECT remote_id, count(*) AS cnt FROM ezcontentobject GROUP BY remote_id HAVING count(*) > 1;

This isn't enough to get things working, though, because if you jump 2 lines higher where the DB object is instantiated and follow that with a simple "who are you" query

print( $db->databaseName() );

you'll be answered with "mysql" on my system, which is a bit odd since it's not even installed.

Forgive my saying something critical here, but do you guys even have a QA for PostgreSQL support? I chose to deploy this product exactly because it claimed to use PG, but in several years of use, I think the only script which has ever run without my intervention has been runcronjobs.php. And even that won't obey the --quiet option any more.

Andy

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu