Jeremey, thanks so much for replying to my question!
Does it also work with em-mysql (if not, it could be
that sequel is trying to load that)?
em-mysql isn't really a standalone mysql driver. It requires
mysqlplus itself to work.
Can you try using the RUBYLIB
environment variable and
On Jul 2, 12:08 pm, Steve H p.wi...@gmail.com wrote:
Can you try using the RUBYLIB
environment variable and make sure that one of the working mysql
libraries first?
I tried this. It didn't work, but maybe I was doing something wrong?
$ gem which mysql
(checking gem mysql-2.7 for
Hmmm. Perhaps I missed something, but Sequel::Migrator is not
defined:
require 'sequel'
= true
DB = Sequel.connect(:adapter = 'mysql', :user = 'root', :database =
'castle_gameserver')
= #Sequel::MySQL::Database: mysql:root@/castle_gameserver
Sequel::Migrator.apply(DB,
Ahh! Aman to my rescue. Glad you're on this list as well as the EM
one :)
Yes, I installed the pure ruby mysql driver back when I had
accidentally downloaded and installed MySQL x86_64, and my connection
was super slow so I didn't replace it with x86 right away.
I installed the pure ruby
On Thu, Jul 2, 2009 at 1:58 PM, Steve Hp.wi...@gmail.com wrote:
Ahh! Aman to my rescue. Glad you're on this list as well as the EM
one :)
Yes, I installed the pure ruby mysql driver back when I had
accidentally downloaded and installed MySQL x86_64, and my connection
was super slow so I
Aman, Jeremy, thanks so much!
I deleted that mysql.rb file, and migrations are running quite nicely
from both the command line utility and from within irb as well now. I
have *other* problems now, but at least this one is solved.
Cheers!
-Steve
On Jul 2, 1:59 pm, Aman Gupta
On Jun 30, 11:59 pm, Steve H p.wi...@gmail.com wrote:
Hey everyone,
I'm brand new to Sequel (as of like a few days ago). So far, I'm
really kind of loving it!! I do wish the docs were a little better
organized/more extensive, but it's hard to complain. At least there
ARE docs. :D
