Hi, when creating a MySQL resource Sequesl loads "mysql". Could it be 
configurable to load "mysql" or "mysqlplus"?

A workaround is requiring "mysqlplus" before loading "sequel". However it 
causes lots of warnings at startup as both libraries share same symbols.

Also, there is a bug in mysqlplus when running under ruby 1.9 since mysqlplus 
contains a line "require 'mysl'" in orde to load *its* own "mysql.so". But due 
to PATH in ruby1.9 it loads the "normal" mysql gem in fact:

  http://github.com/oldmoe/mysqlplus/issues/#issue/2

In ruby1.8 it works since "require 'mysql'" in lib/mysqlplus.rb loads its 
library so next call to "require 'mysql'" in Sequel returns false. This is: 
mysqlplus is working.
But in ruby1.9 it doesn't occur and instead when Sequel does "require 'mysql'" 
it replaces mysqlplus with the normal mysql gem.

So it oculd be great if Sequel could load "mysql" or "mysqlplus" instead of 
always requiring "mysql".

Regards.

-- 
Iñaki Baz Castillo <[email protected]>

--

You received this message because you are subscribed to the Google Groups 
"sequel-talk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sequel-talk?hl=en.


Reply via email to