> Probably an omission.  If you can send a backtrace with that error
> message, I'll take a look.

Sure (from hoptoad - is sequel 3.19.1 because it is git HEAD that I've
packaged as gem):

Sequel::DatabaseError: Mysql::Error: Lost connection to MySQL server
during query
... /vendor/bundle/ruby/1.8/gems/sequel-3.19.1/lib/sequel/adapters/
mysql.rb:200:in `query'
... /vendor/bundle/ruby/1.8/gems/sequel-3.19.1/lib/sequel/adapters/
mysql.rb:200:in `_execute'
... /vendor/bundle/ruby/1.8/gems/sequel-3.19.1/lib/sequel/database/
logging.rb:28:in `log_yield'
... /vendor/bundle/ruby/1.8/gems/sequel-3.19.1/lib/sequel/adapters/
mysql.rb:200:in `_execute'
... /vendor/bundle/ruby/1.8/gems/sequel-3.19.1/lib/sequel/adapters/
mysql.rb:184:in `execute'
... /vendor/bundle/ruby/1.8/gems/sequel-3.19.1/lib/sequel/
connection_pool/threaded.rb:84:in `hold'
... /vendor/bundle/ruby/1.8/gems/sequel-3.19.1/lib/sequel/database/
connecting.rb:226:in `synchronize'
... /vendor/bundle/ruby/1.8/gems/sequel-3.19.1/lib/sequel/adapters/
mysql.rb:184:in `execute'
... /vendor/bundle/ruby/1.8/gems/sequel-3.19.1/lib/sequel/dataset/
actions.rb:541:in `execute'
... /vendor/bundle/ruby/1.8/gems/sequel-3.19.1/lib/sequel/adapters/
mysql.rb:440:in `execute'
... /vendor/bundle/ruby/1.8/gems/sequel-3.19.1/lib/sequel/adapters/
mysql.rb:366:in `fetch_rows'
... /vendor/bundle/ruby/1.8/gems/sequel-3.19.1/lib/sequel/dataset/
actions.rb:123:in `each'
... /vendor/bundle/ruby/1.8/gems/sequel-3.19.1/lib/sequel/dataset/
actions.rb:449:in `single_record'
... /vendor/bundle/ruby/1.8/gems/sequel-3.19.1/lib/sequel/dataset/
actions.rb:457:in `single_value'
... /vendor/bundle/ruby/1.8/gems/sequel-3.19.1/lib/sequel/dataset/
actions.rb:200:in `get'
...

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