I migrated to MySQL about 6 months ago and man would that write-up have
been helpful.  I ran into every problem you addressed.  However...

I was migrating my existing 0.13.0 installation to a new Win2k8 box and
upgrading to 0.16.3.  The problem was located with database.  There was
some corruption in my mysql schema when I dumped all my databases
together.  

I started the mysql server install over from scratch.  I dumped just my
instiki database, imported it to the new server, added my instiki user to
the mysql.user table, and appropriated rights for my instiki database to
that user.

Instiki was not to blame.  Although I did notice that while running on
Windows some of the bundled plugins did not work so I have to "gem
install" rack and activerecord.

Thanks for the quick feedback and help!

Instiki-users <[email protected]> writes:
>On Wed, Mar 4, 2009 at 4:13 PM, Joel W. Garman <[
>mailto:[email protected] ][email protected]> wrote:
>
>
>I'm migrating instiki from a WinXP box to a Win2k8 box as well as
>upgrading to 0.16.3.  I am running MySQL and have moved the database
>successfully.  I unzipped instiki and modified database.yml.  When I run
>instiki.cmd it looks like the app starts up although I did notice it says
>Rails 2.3.0 not 2.3.1.  When I navigate to localhost:2500 I receive this
>error:
>
>
> 
>I found the migration process (on Windows) from 0.10.2 to 0.16.3 to be
>particularly painful (and at the end I still have a lot of orphaned
>pages).
>
>Some things I hit:
>
>- had to manually issue "gem install rack"
>
>- had to manually install sqlite ... i also used gem install to get
>native sqlite bindings (due to some warnings) but the latest sqlite3-ruby
>(1.2.4) requires you to compile sqlite / ruby from sources. I had to
>install sqlite3-ruby 1.2.3 instead which didnt impose this requirement
>
>- the migration read me gives example for windows to run
>script\import_storage which uses "\" slashes in the directory names, but
>the script requires that you use "/" slashes or it generates errors.
>
>- the script reset_references is pointed at the development database and
>not the production database contrary to what the readme states. You can
>either edit the second line of the script and change 'development' to
>'production' or copy your database to the development referenced one in
>database.yml...
>
>- I also was getting errors from reset_references in the line that reads
>(I cant recall the error message):
>Web.find_all.each do |web|
>
>I had to change this to:
>Web.find(:all).each do |web|
>
>
>
>There may have been more, but those are what I recall. 
>
>
>
>_______________________________________________
>Instiki-users mailing list
>[email protected]
>http://rubyforge.org/mailman/listinfo/instiki-users

_______________________________________________
Instiki-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/instiki-users

Reply via email to