Databases
StackOverflow2013
Postsdbo
POError: operator does not exist: character varying = integer
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POError: operator does not exist: character varying = integer
    primarykey
    data
    text
    <p>I face a common problem. My Rails app works on my local machine, but after deploying to heroku it crashes:</p> <pre><code>&lt;% unless @user.hotels.empty? %&gt; &lt;% @user.hotels.each do |hotel| %&gt; &lt;%= "#{hotel.description} #{hotel.name} in #{hotel.city}, #{hotel.country}" %&gt;&lt;br /&gt; &lt;% end %&gt; &lt;% end %&gt; </code></pre> <p>This is from the heroku logs:</p> <pre><code>ActionView::Template::Error (PGError: ERROR: operator does not exist: character varying = integer LINE 1: SELECT "hotels".* FROM "hotels" WHERE ("hotels".user_id = 1) ^ HINT: No operator matches the given name and argument type(s). You might need to add explicit type casts. : SELECT "hotels".* FROM "hotels" WHERE ("hotels".user_id = 1)): </code></pre> <p><code>@user.hotels.empty?</code> creates the error. I know, sqlite is pretty forgiving, but PostgreSQL is not. This is the foreign key in the hotel model: <code>user_id :integer</code></p> <p>Heroku says:</p> <pre><code>Make sure the operator is adequate for the data type. ActiveRecord does this automatically when you use an interpolated condition form. Array conditions: :conditions =&gt; ['column1 = ? AND column2 = ?', value1, value2] Hash conditions: :conditions =&gt; { :column1 =&gt; value1, :column2 =&gt; value2 } </code></pre> <p>The migration looks like following:</p> <pre><code>class CreateHotels &lt; ActiveRecord::Migration def self.up create_table :hotels do |t| t.string :name t.string :vanity_url t.integer :user_id .... </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USLukas Hoffmann
    1. USLukas Hoffmann
    plurals
    1. PL
      singulars
      1. LTLinked
    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. POError: operator does not exist: character varying = integer
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POError: operator does not exist: character varying = integer
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POError: operator does not exist: character varying = integer
      1. This table or related slice is empty.
      1. VTUpMod
    1. COJust looking at the error message, it sure looks like Postgres considers hotels.user_id to be a varchar.
      singulars
      1. POError: operator does not exist: character varying = integer
      1. USjohusman
    2. COhm, but in the hotel model it is set as integer.
      singulars
      1. POError: operator does not exist: character varying = integer
      1. USLukas Hoffmann
    3. COWhat is the data type of user_id **in the database**? The rails model is not important for this error message.
      singulars
      1. POError: operator does not exist: character varying = integer
      1. USa_horse_with_no_name
 

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