Here you are: http://svn.apache.org/r1562380
On Tue, Jan 28, 2014 at 11:05 PM, Peter Dähn <[email protected]> wrote: > Hi Maxim, > > that sounds perfect... :-) > > So we wait for the patches... > > Thanks Peter > > > Am 28.01.2014 16:56, schrieb Maxim Solodovnik: > > Good finding > I can fix 3.0 and send you revision number and you patch 2.0/2.2 > is it Ok? > > > On Tue, Jan 28, 2014 at 10:54 PM, Peter Dähn <[email protected]> wrote: > >> Hi Maxime... >> >> according to this... >> http://stackoverflow.com/questions/6585574/postgres-default-sort-by-id-worldshippostgres >> returns a not sortet result... so the xml is scambled... :-( >> >> how to fix export or import? >> >> We think a "sort by id" in the export functions (it seems to be a problem >> with all exports... rooms, user, flvs, messages... ) could do the job... >> >> Could you give us a hind where we can find the used functions? >> >> BR Peter >> >> >> Am 28.01.2014 16:01, schrieb Peter Dähn: >> >> no.. unfortunately not.. the same order than the xml... >> >> maybe something different because we use postgres-db? >> >> >> Am 28.01.2014 15:45, schrieb Maxim Solodovnik: >> >> Are your ids goes one-by-one? >> >> >> On Tue, Jan 28, 2014 at 9:25 PM, Peter Dähn <[email protected]> wrote: >> >>> i allready had a look at the dbs... the ids are different... >>> >>> and I also droped the db before restore om... :-( >>> >>> anyway... sounds not good for me... :-( >>> >>> >>> Am 28.01.2014 15:20, schrieb Maxim Solodovnik: >>> >>> In this case >>> all rooms should have same ids after import >>> >>> could you perform select from the database to check? >>> have you dropped your Db before import? >>> >>> >>> On Tue, Jan 28, 2014 at 9:14 PM, Peter Dähn <[email protected]> wrote: >>> >>>> hmm... i never put my hands on the database somehow... >>>> >>>> Am 28.01.2014 15:02, schrieb Maxim Solodovnik: >>>> >>>> the only case it can "scramble" ids: you have manually "hard" deleted >>>> some rooms >>>> >>>> >>>> On Tue, Jan 28, 2014 at 8:57 PM, Peter Dähn <[email protected]> wrote: >>>> >>>>> thats what i did before... and it will scramble the roomIDs... :-( >>>>> >>>>> any other ideas? >>>>> >>>>> BR Peter >>>>> >>>>> Am 28.01.2014 14:49, schrieb Maxim Solodovnik: >>>>> >>>>> -f option for file clean up only >>>>> >>>>> you need: "./admin.sh -i -v -file backup_31_07_2012_12_07_51.zip >>>>> --drop" >>>>> >>>>> >>>>> On Tue, Jan 28, 2014 at 8:39 PM, Peter Dähn <[email protected]> wrote: >>>>> >>>>>> Hi Maxim... >>>>>> >>>>>> according to Admin.java 199 >>>>>> >>>>>> Command cmd = Command.usage; >>>>>> if (cmdl.hasOption('i')) { >>>>>> cmd = Command.install; >>>>>> } else if (cmdl.hasOption('b')) { >>>>>> cmd = Command.backup; >>>>>> } else if (cmdl.hasOption('r')) { >>>>>> cmd = Command.restore; >>>>>> } else if (cmdl.hasOption('l')) { >>>>>> cmd = Command.languages; >>>>>> } else if (cmdl.hasOption('f')) { >>>>>> cmd = Command.files; >>>>>> } >>>>>> >>>>>> -f option will be ignored in case of -i... Am I right? >>>>>> >>>>>> BR Peter >>>>>> >>>>>> Am 28.01.2014 14:12, schrieb Maxim Solodovnik: >>>>>> >>>>>> yes >>>>>> It will not create any additional users, just will add the contents >>>>>> of backup file >>>>>> >>>>>> >>>>>> On Tue, Jan 28, 2014 at 7:59 PM, Peter Dähn <[email protected]> wrote: >>>>>> >>>>>>> Hi Maxim, >>>>>>> >>>>>>> thanks for your quick response. >>>>>>> >>>>>>> Do you mean by "install from file" the -f option of admin.sh? >>>>>>> >>>>>>> something like "./admin.sh -i -v -f -file backup.zip" >>>>>>> >>>>>>> BR >>>>>>> >>>>>>> Peter Dähn >>>>>>> >>>>>>> Am 28.01.2014 13:43, schrieb Maxim Solodovnik: >>>>>>> >>>>>>> you can try to "install from file" >>>>>>> This is the only way I know to preserve room ids >>>>>>> >>>>>>> >>>>>>> On Tue, Jan 28, 2014 at 7:40 PM, Peter Dähn <[email protected]> wrote: >>>>>>> >>>>>>>> >>>>>>>> Hallo together, >>>>>>>> >>>>>>>> I faced a problem while import a backup from 2.0 to 2.2. >>>>>>>> >>>>>>>> The roomIDs were scrambled during import. This happens because the >>>>>>>> new >>>>>>>> IDs will be created because of the order of the rooms in room.xml. >>>>>>>> >>>>>>>> The problem is, that we store the further roomIDs in the database >>>>>>>> of >>>>>>>> our LMS and use them to launch a room directly. And after the >>>>>>>> update the >>>>>>>> user enter the wrong room. >>>>>>>> >>>>>>>> Maybe "r.setRooms_id(null);" Line 289 in BackupImportController.java >>>>>>>> causes the trouble. It seems there were all further roomIDs >>>>>>>> discarded. >>>>>>>> >>>>>>>> Any Ideas how to handle it? >>>>>>>> >>>>>>>> BR >>>>>>>> Peter Dähn >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> WBR >>>>>>> Maxim aka solomax >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> WBR >>>>>> Maxim aka solomax >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> WBR >>>>> Maxim aka solomax >>>>> >>>>> >>>> >>>> >>>> -- >>>> WBR >>>> Maxim aka solomax >>>> >>>> >>> >>> >>> -- >>> WBR >>> Maxim aka solomax >>> >>> >> >> >> -- >> WBR >> Maxim aka solomax >> >> >> > > > -- > WBR > Maxim aka solomax > > -- WBR Maxim aka solomax
