![]() ![]() First things first, some versions (Just in case it's important I just pasted the final text that was produced into that, and ran the took a while, but worked a treat. ![]() Hoope this helps!īTW if you have phpMyAdmin installed, it has a handy little SQL window you can use for executing SQL commands. I hope you have a db backup and file backup of your 1.8 site, because i"ll have the excel file posted sometime later today when I get the bugs (and my site's information) worked out of it. Presto! the whole database finally ended up in unicode, and the 1.9 upgrade worked flawlessly. I had copied my entire production server to a second server to trial the 1.9 beta and did this on the trial server. Someone whou has the skills to convert this to an openoffice macro might find a prettier solution than that, but I only have skills in VBA.sorry!īTW my VBA skills aren't prodigious, someone might be able to tweak this macro to do the whole thing in one shot, I'm not that good! I used a tab delimited text save in Excel, since it didn't have pipe delimited, I needed to use Word to strip the tabs, and that was a bit of a pain, but not too messy. This file (which I'm just tweaking so that everything happens in one macro) produces the SQL commands, if you save it as a text formatted file (preferably something other than comma delimited) and strip out all the delimiters using a find-replace, it'll give you a working SQL statement for every table and field in your database. Using macros, and the SQL commands on the SQL commands sheet in the spreadsheet, I stripped out everything that I didn't want, and formatted all the SQL statements so that they would work. I noticed that the comma delimiters weren't recognised by excel for the tables, so I copied the table cells to text editor, saved it as a CSV, opened it up in excel and copied all the cells from there to cell a1 again, overwriting the existing table names. I copied THE ENTIRE WINDOW'S TEXT and pasted it into cell a1 of the moodle sheet in the excel worksheet I will be uploading soon Using phpMyAdmin (It's important that you use phpMyAdmin for this step as the excel file i will upload when I've finished tweaking the macros, relies on the formatting that phpMyAdmin uses) I opened the print view of every table in the database, you can do this by selecting all the tables in database view and using the listbox at the bottom of the screen to select print view. I fixed it in the following way (Purists block your ears, you'll hear a fair few Microsoft names in the next couple of minutes. It appears that 1.8 will run OK with a Unicode database that has fields and tables in general, or at least mine didn't break until I tried to upgrade to 1.9! I guess this came about because I had some issues early in my 1.8 days and had to do a fair bit of restoration from old backups, and hacking the database. It turned out that my database was INDEED in UTF8 General. I had a similar issue.I discovered it trying to upgrade from 1.8.4 to 1.9 beta, the upgrade stalled when unicode wasn't found. this all started when i tried an update to 1.9 and it terminated in an error - do you think that's how i got into this mess in the first place and if so, would the best/only thing to do be to go back to 1.7? So, i'm thinking i'll do the "go back to 1.7 to get to 1.8/9 thing. When i get done with this, the tables are all there, they show in phpymadmin as having the utf8_general_ci collation sequence, but moodle still believes the database is not a unicode database. sql file creates every table in whatever collation the original table was (utf8_unicode_ci) use mysql -user=username -password=userpassword create a new database with the utf8_general_ci collation.So, what I've done to do the recovery was: I have turned off the moodle backup process and have written my own cron jobs that back up the site files, site data and the moodle database. Thanks for your attentiveness to this problem. I made a stand by on my upgrade test, since I do not have the time now to upgrade.but I would love to know how to do it right! Was my creation command on the sheel mysqladmin. I supose the error was that when I create the new DB (moodle19), I have to define it as unicode. I had the same problem: the upgrade told me that the DB was not on unicode. Then I copied moodledata and the moodle files (to /data/moodledata1 and to /var/www/moodle19) to a different directory and performed the upgrade on the copy of the moodle site. I did this in order to do a test of the upgrade in the same server (I do not have another one) I created a new DB (name of the DB: moodle19) on mysqladmin (no interface, really on the shell) I made a dump of the database on 1.7.1+ (name of the DB: moodle17)Ģ. I think I had the same problem when I made my test upgrade from 1.7.1+ to 1.9ġ. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |