2010-08-09 12:10:38
Hi
We are moving from Atutor 1.6.1 to 2.0 (and moving servers)
Is there a way to export the user database?
Or will it just have to be done manually?
If manually, is it just the 'AT_members' table that needs exporting?
2010-08-10 07:14:49
Ok, Just in case anyone else searches for this.
I exported the user list from AT_members table and imported it into my new AT install, all appears to be working ok.
Couple of point for others :
A direct MySQL export and import of the table data failed, so I had to export as CSV and import that.
This may have been down to using differant MySQL versions (althow both were 5 releases) or it could just have been the front end I used to export/import the data (export with phpmyadmin, import with webmin)
The other problem was that the member_id numbers in AT_members clashed, this was becasue I had added a couple of users to the new install to test it.
And the imported data had users with the same ID number, I got around this by just deleteing the test users I had created before importing my old user data.
One thing to watch for, is the course owner uses this ID number, so if you remove your test users, and import your old users, make sure you double check who owns the courses etc.
Matt
2010-08-10 08:23:18
I think another option would be to upgrade to the new version, and then move the upgraded database to the new server. Of course, I don't know if that was possible/needed in this particular case.
Also, when exporting via CSV there might be a problem with new users.
For each table MySQL internally keeps a counter that tells it the last ID that has been assigned. So, if you had e.g. 1000 users in the older DB and 5 in the newer one, and then just copied the table over via a CSV file, the counter in the new DB would remain at "5". And the next time you add a user to the new installation, MySQL will try to create a user with ID 6.
I think that MySQL's engine is intelligent enough to do something about that, but it's still best to copy an old table by generating a SQL file (which should contain a query to create a new table -- there is such an option in phpMyAdmin), then delete the target table and import the SQL file in its place.