We will be still testing migration for some time, because we haven't moved BASE1 to the new server yet. Some additional code was needed to move our local adaptations. They are supposed to be a part of 1.2.18 BASE1 release (if happens), so if anyone ever needs to migrate from that version, we might have the code.
We are also working now on task of merging two (or more?) BASE1 installations into one BASE2, using migration package. Do you know of any issues that could be problematic in this case? I managed to run one migration after another (from different BASE1s), after minor code changes, but still need to check if some items do not clash somehow. Anyway, we are still working with migration so if anything serious pops up, I will let you know. Of course, if any of features I mentioned above is interesting for you, we will be glad to contribute to the project. All the best and have a nice Easter, Pawel Nicklas Nordborg wrote: > Pawel Sztromwasser wrote: >> Hi, >> >> While testing migration I found out that items deleted in BASE1 are >> migrated to BASE2. As I understand from documentation, BASE1 doesn't >> delete items from the database unless purgeDatabase.php script is >> executed. They are just flagged as deleted by setting remove value=2 (or >> > 1 maybe). Those that have removed flag set to 1 are marked for >> deletion (something equivalent to moving to trashcan). Other items have >> removed=0. >> >> Migration code uses ResultSet.getBoolean() method to retrieve 'removed' >> value (which is smallint) and as I checked, it returns true only when >> removed==1. The consequence is that items marked for deletion go to >> trashcan as they suppose to, but those actually deleted get removed flag >> set to false and appear in BASE2 as not deleted. >> >> This could be due to postgres JDBC driver handling type mapping in >> different way than mysql driver, but I couldn't find any information on >> that. The quick solution is to run purgeDatabase.php before migration to >> remove deleted items from the database. > > I didn't know that. I simply assumed that the removed flag only could be > 0 or 1. Kind of like in BASE2. In any case, the 2.6 release was the > latest release of the migration program. It will still be included in > future releases, but we will not test or actively maintain it anymore. > The reason for this is that we are moving our servers to BASE 2, and at > some time in the future we will not have a BASE 1 server to use for > testing the migration. > > Should any remaining critical bugs appear we will of course assist in > fixing it. > > /Nicklas > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > basedb-devel mailing list > basedb-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/basedb-devel ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ basedb-devel mailing list basedb-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/basedb-devel
