Databases
StackOverflow2013
Postsdbo
PORuby gem Error "Google is not a module/class"
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORuby gem Error "Google is not a module/class"
    primarykey
    data
    text
    <p>When I first require 'roo' and then require 'google-search' I get an error </p> <pre><code>TypeError: Google is not a module </code></pre> <p>Again, I first require 'google-search' and then require 'roo' I get this error</p> <pre><code>TypeError: Google is not a class </code></pre> <p>See below for what actually happened on irb</p> <pre><code>{12:30}[1.9.3]~ ➭ irb 1.9.3-p0 :001 &gt; require 'roo' =&gt; true 1.9.3-p0 :002 &gt; require 'google-search' TypeError: Google is not a module from /home/sagar/.rvm/gems/ruby-1.9.3-p0/gems/google-search-1.0.3/lib/google-search/version.rb:2:in `&lt;top (required)&gt;' from /home/sagar/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:55:in `require' from /home/sagar/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:55:in `require' from /home/sagar/.rvm/gems/ruby-1.9.3-p0/gems/google-search-1.0.3/lib/google-search.rb:26:in `&lt;top (required)&gt;' from /home/sagar/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:59:in `require' from /home/sagar/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:59:in `rescue in require' from /home/sagar/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:35:in `require' from (irb):2 from /home/sagar/.rvm/rubies/ruby-1.9.3-p0/bin/irb:16:in `&lt;main&gt;' 1.9.3-p0 :003 &gt; exit {12:30}[1.9.3]~ ➭ irb 1.9.3-p0 :001 &gt; require 'google-search' =&gt; true 1.9.3-p0 :002 &gt; require 'roo' TypeError: Google is not a class from /home/sagar/.rvm/gems/ruby-1.9.3-p0/gems/roo-1.10.1/lib/roo/google.rb:7:in `&lt;top (required)&gt;' from /home/sagar/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:55:in `require' from /home/sagar/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:55:in `require' from /home/sagar/.rvm/gems/ruby-1.9.3-p0/gems/roo-1.10.1/lib/roo.rb:74:in `&lt;top (required)&gt;' from /home/sagar/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:59:in `require' from /home/sagar/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:59:in `rescue in require' from /home/sagar/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:35:in `require' from (irb):2 from /home/sagar/.rvm/rubies/ruby-1.9.3-p0/bin/irb:16:in `&lt;main&gt;' </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USsagar junnarkar
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORuby gem Error "Google is not a module/class"
      1. USsagar junnarkar
      1. VTFavorite
    2. VO
      singulars
      1. PORuby gem Error "Google is not a module/class"
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PORuby gem Error "Google is not a module/class"
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload