Databases
StackOverflow2013
Postsdbo
POSequel default example fails when switched to postgres adapter
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSequel default example fails when switched to postgres adapter
    primarykey
    data
    text
    <p>I'm trying to run the Sequel example from <a href="http://sequel.rubyforge.org/" rel="nofollow">http://sequel.rubyforge.org/</a>. Everything works fine on sqlite, but fails when I switch to postgres.</p> <p>This is the connection code:</p> <pre><code>DB = Sequel.connect(:adapter=&gt;'postgres', :host=&gt;'localhost', :database=&gt;'testing', :user=&gt;'postgres', :default_schema=&gt;'sequel') </code></pre> <p>This is the error I get:</p> <pre><code>postgres.rb:145:in `async_exec': PG::Error: ERROR: relation "items" does not exist (Sequel::DatabaseError) LINE 1: INSERT INTO "items" ("price", "name") VALUES (12.45377636338... </code></pre> <p>I'm suspecting that the issue is Sequel trying to execute INSERT INTO <em>"items"</em> instead <em>"sequel.items"</em>, even though :default_schema is correctly set.</p> <p>Anyone have any idea what i'm doing wrong? Thanks in advance.</p> <p>Edit - this is the code used:</p> <pre><code>require "rubygems" require "sequel" # connect to an in-memory database #DB = Sequel.sqlite DB = Sequel.connect(:adapter=&gt;'postgres', :host=&gt;'localhost', :database=&gt;'testing', :user=&gt;'postgres', :default_schema=&gt;'sequel') # create an items table DB.create_table :items do primary_key :id String :name Float :price end # create a dataset from the items table items = DB[:items] # populate the table items.insert(:name =&gt; 'abc', :price =&gt; rand * 100) items.insert(:name =&gt; 'def', :price =&gt; rand * 100) items.insert(:name =&gt; 'ghi', :price =&gt; rand * 100) # print out the number of records puts "Item count: #{items.count}" </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USddario
    1. USddario
    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. This table or related slice is empty.
    1. COUsually this error is a sign that you did not run your latest migrations. Try running `rake db:migrate` again.
      singulars
      1. POSequel default example fails when switched to postgres adapter
      1. USThomas Klemm
    2. COI don't have rake set up for this, it's just a simple script. Anyway tables are created correctly, it fails on the 'insert' part.
      singulars
      1. POSequel default example fails when switched to postgres adapter
      1. USddario
    3. COWe need to see a migration showing the table names and columns plus your model, or a schema dump, plus your Sequel statement you're using to insert. This error could occur because of a model mismatch with a table, or a bad Sequel insert statement.
      singulars
      1. POSequel default example fails when switched to postgres adapter
      1. USthe Tin Man
 

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