[
https://issues.apache.org/jira/browse/OPENMEETINGS-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262442#comment-13262442
]
SebastianWagner commented on OPENMEETINGS-232:
----------------------------------------------
Hi Maxim,
I don't want to change the IDs as all old plugins won't work then and everybody
has to change his integration code.
We could make the room_type_id to be _not_ the primary_key.
> Rooms are imported with invalid room types
> ------------------------------------------
>
> Key: OPENMEETINGS-232
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-232
> Project: Openmeetings
> Issue Type: Bug
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: Maxim Solodovnik
> Assignee: Maxim Solodovnik
> Priority: Blocker
>
> since room type "audience (with id 2)" is removed we need mechanism of
> mapping room types.
> Steps:
> 1) OM prior to 2.0 is backed up
> 2) OM 2.0 is unpacked
> 3) data gets imported
> 4) rooms get invalid room types
> Room export xml has RoomTypeId
> room types 2 and 5 were removed.
> The only option I see is to add
> <version value="2.0"> to the xml
> so xml will look like follows:
> <root>
> <rooms>
> <version value="2.0">
> <room>
> ......
> </room>
> <room>
> ......
> </room>
> <room>
> ......
> </room>
> </rooms>
> </root>
> this will help us to see if this node is missing or version is less than 2.0
> we will map all 5 types if it is 2.0 we will map 3 types only
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
