Forums | Admin

Discussion Forums: open-discussion

Start New Thread Start New Thread
Message: 90135
BY: Mike Pomraning (pilcrow)
DATE: 2009-09-06 14:50
SUBJECT: RE: DBI.connect error-uninitialized Mysql:Driver

 

> ruby -rmysql -e 'p Mysql::VERSION'
> -e:1:in `<main>': uninitialized constant
> Mysql::VERSION (NameError)

``require "mysql"'' is not giving a fatal error, but it is not finding the mysql-ruby package that we expect. ``DBI.connect("dbi:Mysql...")'' gives you a different error, but I'd similarly suspect that it is silently failing to find dbd/Mysql.rb.

I think if you can solve why the ``p Mysql::VERSION'' test didn't work, you'll have
found the problem for ``DBI.connect()'' as well.

However, this seems squarely an installation problem now. The answer is somewhere in

$ ruby -rmysql -e 'puts $"'
-or-
$ strace -s 1024 -e trace=file -rmysql -e 0

but may take a while to find.

-Mike


Thread View

Thread Author Date
DBI.connect error-uninitialized Mysql:DriverHelio Rodrigues2009-07-30 14:08
      RE: DBI.connect error-uninitialized Mysql:DriverMike Pomraning2009-09-06 05:08
      RE: DBI.connect error-uninitialized Mysql:Driver~ ~2009-09-05 20:06
            RE: DBI.connect error-uninitialized Mysql:DriverMike Pomraning2009-09-06 05:19
                  RE: DBI.connect error-uninitialized Mysql:Driver~ ~2009-09-06 10:23
                        RE: DBI.connect error-uninitialized Mysql:DriverMike Pomraning2009-09-06 14:50
                              RE: DBI.connect error-uninitialized Mysql:Driver~ ~2009-09-07 10:31
            RE: DBI.connect error-uninitialized Mysql:DriverMike Pomraning2010-05-25 04:10

Post a followup to this message