Forums | Admin

Discussion Forums: open-discussion

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

 

Helio,

Your installation is suspect. My suggestion is to wipe your ruby install and start over, *without* installing any dbi or dbd modules under site_ruby.

Rationale:

You have a "site_ruby" dbi (installed under lib/ruby/site_ruby/1.8) which is blocking ruby's view of the "gem" dbi (v0.4.2, installed under lib/ruby/gems/1.8/gems).

You have also manually copied a single file from a multi-file gem library to the site_ruby tree. Don't do that, please! :)

The "site_ruby" dbi is perhaps ancient -- we don't know its version from the information you've posted, but we do know it doesn't understand DBI::TypeUtil. (Is it the dbi-0.2.2 that ships with the ruby-1.8.6-p??? installer for Windows, out of curiosity?) This isn't the dbi you want.

Regards,
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