Openfire (ARCHIVED)

Allow to install Openfire and Clearspace in the same database

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 3.5.0
  • Fix Version/s: 3.6.0
  • Component/s: Core, Database
  • Labels:
    None
  • Acceptance Test - Add?:
    No
  • Acceptance Test - Entry:
    Hide

    1. Install CS and OF in the same database
    2. Check that tables were created and no collision exist
    3. Both products should work fine and not share the same tables

    Show
    1. Install CS and OF in the same database 2. Check that tables were created and no collision exist 3. Both products should work fine and not share the same tables

Description

Rename the tables whose name collide with Clearspace. The goal is to be able to install both products in the same databases. Also make sure that the list of supported DBs are the same (i.e. CS is included in OF). For now, Clearspace and Openfire will use their own tables and will not read from each others table. We just need to let admins install them in the same database.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Daniel Henninger added a comment -

If we must do this, I see no reason to pick and choose. We should rename all of the tables across the board to be prefixed with something like of. ofJiveProperties. stuff like that. In my opinion, we should also be renaming the Clearspace tables to have a prefix as well, so as to aim to prevent conflicts in the future.

Also, I don't think it will be a good idea to plan on having CS and OF use the same tables in the future. CS owns it's tables. It knows it's tables. It should be able to freely mess with them without having to be concerned that Openfire (or anything external for that matter) is screwing with it's tables. =) Same goes for Openfire.

Show
Daniel Henninger added a comment - If we must do this, I see no reason to pick and choose. We should rename all of the tables across the board to be prefixed with something like of. ofJiveProperties. stuff like that. In my opinion, we should also be renaming the Clearspace tables to have a prefix as well, so as to aim to prevent conflicts in the future. Also, I don't think it will be a good idea to plan on having CS and OF use the same tables in the future. CS owns it's tables. It knows it's tables. It should be able to freely mess with them without having to be concerned that Openfire (or anything external for that matter) is screwing with it's tables. =) Same goes for Openfire.
Hide
Permalink
Daniel Henninger added a comment -

Obviously we can't force them, but we should also put in the plugin dev docs a recommendation to prefix their plugin tables the same way.

Show
Daniel Henninger added a comment - Obviously we can't force them, but we should also put in the plugin dev docs a recommendation to prefix their plugin tables the same way.
Hide
Permalink
Daniel Henninger added a comment -

Completed and committed to trunk, but through jdbc and apparently through jdbc only, the old table is being left around even after a rename? What sense does that make?

Show
Daniel Henninger added a comment - Completed and committed to trunk, but through jdbc and apparently through jdbc only, the old table is being left around even after a rename? What sense does that make?
Hide
Permalink
Daniel Henninger added a comment -

Found and fixed. Only affects anyone who snuck into SVN for that brief time when it was broken.

Show
Daniel Henninger added a comment - Found and fixed. Only affects anyone who snuck into SVN for that brief time when it was broken.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for igniterealtime.org. Try JIRA - bug tracking software for your team.