Databases
StackOverflow2013
Postsdbo
POhas_one :conditions being interpreted as attributes?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POhas_one :conditions being interpreted as attributes?
    primarykey
    data
    text
    <p>This association:</p> <pre><code>class Business &lt; ActiveRecord::Base has_one :map_address, :as=&gt;:addressable, :class_name =&gt; 'Address', :conditions =&gt; {'addresses.map_address'=&gt;true}, :dependent =&gt; :destroy end </code></pre> <p>Causes this error:</p> <pre><code>ruby-1.8.7-p334 :005 &gt; n = Business.new ruby-1.8.7-p334 :006 &gt; n.build_map_address ActiveRecord::UnknownAttributeError: unknown attribute: addresses.map_address </code></pre> <p>The code used to read </p> <pre><code>:conditions =&gt; {:map_address=&gt;true} </code></pre> <p>But the lack of table name causes this issue on lookup (it's putting the field name on the wrong table): </p> <pre><code>ActiveRecord::StatementInvalid (PGError: ERROR: column counties.map_address does not exist ^ SELECT "businesses".* FROM "businesses" INNER JOIN "addresses" ON ("businesses"."id" = "addresses"."addressable_id" AND "addresses"."addressable_type" = 'Business') INNER JOIN "counties" ON ("counties"."id" = "addresses"."county_id") AND counties."map_address" IS NULL WHERE (counties.id = 23) ORDER BY businesses.updated_at DESC): </code></pre> <p>This option:</p> <pre><code>"adresses.map_address is true" </code></pre> <p>produces this error on lookup:</p> <pre><code>PGError: ERROR: missing FROM-clause entry for table "adresses" LINE 1: ..." ON ("states"."id" = "addresses"."state_id") AND adresses.m... ^ : SELECT "businesses".* FROM "businesses" INNER JOIN "addresses" ON ("businesses"."id" = "addresses"."addressable_id" AND "addresses"."addressable_type" = 'Business') INNER JOIN "states" ON ("states"."id" = "addresses"."state_id") AND adresses.map_address is NULL WHERE (states.id = 4) ORDER BY businesses.updated_at DESC </code></pre> <p>So my question is why is rails trying to turn this condition into an attribute? And how can I make it work both ways? My guess is that rails is trying to set the condition up as a default value for the new record.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USpixelearth
    1. USpixelearth
    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
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POhas_one :conditions being interpreted as attributes?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POhas_one :conditions being interpreted as attributes?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COOk, nevermind, I found that the misinterpretation of the table name was actually coming from searchlogic, so this isn't a rails issue, after all. :(
      singulars
      1. POhas_one :conditions being interpreted as attributes?
      1. USpixelearth
    2. COSo what's the correct code look like?
      singulars
      1. POhas_one :conditions being interpreted as attributes?
      1. USIntentss
 

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