Schemas in 2.4 source tarball marked as version 2.2

Openfire Openfire Support
1

All of the wildfire_src/src/database/wildfire_*.sql[/b] files contain INSERT INTO jiveVersion (majorVersion, minorVersion) VALUES (2, 2)[/b]

Should this be (2,4)?

I’'m seeing:

2005.12.18 07:40:09 Found old database schema (2.2). Upgrading to latest schema.

2005.12.18 07:40:09 Warning: Make sure that database was not modified for release: 2.3. Upgrade script not found: /database/upgrade/2.2_to_2.3/wildfire_mysql.sql

2005.12.18 07:40:09 Warning: Make sure that database was not modified for release: 2.4. Upgrade script not found: /database/upgrade/2.3_to_2.4/wildfire_mysql.sql

2005.12.18 07:40:09 Database upgraded successfully.

in the ‘‘info’’ log as a result.

2

Hmm, I just encountered this and concluded that there was a missing upgrade script rather than thinking that the DB version numbering was wrong.

So where’'s the missing script?

3

Hi Roger,

Good catch, looks like the scripts didn’‘t get upgraded and were inserting the wrong version. I’'ve fixed the scripts in subversion.

Thanks,

Ryan

4

Hi Dan,

There was never a 2.2_to_2.3 upgrade script so that’‘s the reason for the first log message. The most likely reason for the second is that the upgrade scripts aren’'t were Wildfire expects them to be, i.e., WILDFIRE_HOME/resources/database/upgrade.

Regards,

Ryan