Hello developer,

 

Is nobody here who has determined this issue?

 

Darko

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darko
Palic
Sent: Montag, 24. November 2008 14:42
To: [email protected]
Subject: [dev] Huge differences between 2.0.4 to 2.2.4 Upgradepath and the
direct way with otrs-schema.mysql.sql

 

Hello list,

 

First of all: This is not a support request, even if it looks like! I will
post my support questions to the users-ML if necessary, but my issue is the
point with maybe inconsistent DB-scripts in the distributions.

 

Here my scenario:

I am upgrading from otrs 2.0.4 to otrs 2.2.4. And the differences between
creating the database via the upgrade path (DBUpdate-to-2.1.mysql.sql,
DBUpdate-to-2.2.mysql.sql, DBUpdate-to-2.2.2.sql

) to 2.2.4 and the direct create via otrs-schema-mysql.sql/
otrs-schema-post.mysql.sql are huge.

 

A  possible question could be why am I using the old 2.2.4. I have only
hosted ubuntus with the default packages. Therefore I can only use ubuntu
provided packages. And this is currently 2.2.4.

 

The next issue is, that I wanted to migrate my otrs from 2.0.4 to 2.2.4 from
a old to a new server installation/hardware. Therefore I exported my 2 GB
huge otrs 2.0.4 DB and imported it on the new server with 2.2.4. Now I was
trying to run the migration scripts provided with the 2.2.4 distribution
(DBUpdate-to-2.1.mysql.sql, DBUpdate-to-2.2.mysql.sql,
DBUpdate-to-2.2.2.sql). This failed.

 

Therefore I thought it was my fault on any previous installation of otrs.
And I analysed my way.

Here may analysis:

-          Create a initial DB called initial (attached otrs-initial.sql)
with otrs-schema-mysql.sql/otrs-schema-post.mysql.sql from the 2.2.4-tar.gz
distribution

-          Create a migration DB from 1.1.3 to migrate to 2.2.4 called
migration (attached otrs-migration.sql)
with otrs-schema.mysql.sql (from 1.1.3) and the migration scripts
(DBUpdate-to-1.2.mysql.sql, DBUpdate-to-1.3.mysql.sql,
DBUpdate-to-2.0.mysql.sql, DBUpdate-to-2.1.mysql.sql,
DBUpdate-to-2.2.mysql.sql, DBUpdate-to-2.2.2.sql)

 

As you can see the both databases, which in my opinion should be identical
are very very different.

I have also attached a migration-script
(otrs-initial_migrateInitial_ToUpgradePath.sql) which alters the initial DB
to the migration DB. This is only for the purpose to show how huge the
differences are. The script itself makes no sense.

 

As a developer I cannot believe, that this can be correct. What have I done
wrong?

 

So far the questions from my point as a developer. Now my question, how can
I upgrade my otrs 2.0.4 to 2.2.4 with changing the hosted hardware?

 

Best regards,

Darko

PS: this is a double post, due to no reaction of the ML-moderator! Please
answer only on this post.

_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev

Reply via email to