Jeremy, FYI: https://merb.lighthouseapp.com/projects/7435-merb-more/tickets/30-merbsequelmysql-handshake-problem#ticket-30-3
Cheers, Cris On Aug 6, 1:11 am, "cristian.malinescu" <[email protected]> wrote: > Hi Jeremy, > > I placed the code you suggested like this - in my init.rb: > > require 'config/dependencies.rb' > require 'sequel' > > gem('mysql') > > use_orm :sequel > use_test :rspec > use_template_engine :erb > > Merb::Config.use do |c| > p(["MysqlError already defined", __LINE__]) if defined?(MysqlError) > .... > > and the execution doesn't reach it, of course, the warning is still > generated and the mongrel/thin/passenger are dying ... > > On Aug 5, 11:20 am, Jeremy Evans <[email protected]> wrote: > > > On Aug 4, 11:58 pm, "cristian.malinescu" > > > <[email protected]> wrote: > > > Hi, > > > > I try to launch a Merb app where I replaced the default datamapper orm > > > with Sequel, however, I'm stuck at this error: > > > ../gems/mysql-2.7/lib/mysql.so: warning: already initialized constant > > > MysqlError. > > > Well, that's a warning, not an error, so things should still work. Do > > you get this behavior when you use Sequel by itself? If not, it's > > probably a Merb issue. The easiest way to track it down is probably > > adding some print statements to the Merb startup file: > > > p(["MysqlError already defined", __LINE__]) if defined?(MysqlError) > > > That should make it possible to track down where MysqlError is > > originally defined. > > > Jeremy > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
