PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column

Dear Sir/Madam,

I have just downloaded and and am now going to install a nice design theme Designmd01 - Responsive Drupal 7" from themeforest webpage.

[the rest of the post has been cut away by hansfn since it wasn't related to this module]

I had the same problem but using the views entity reference widget with the views field of the title replaced by the title_field solved this. I do not think that this is something to solve in code than in configuration. I guess that #2 may have other reasons. Regards

Related issue: #2102045: Wrong base table - Column not found: 1054 Unknown column 'field_data_XXX.nid' ...

Added multilingual select module to error reproduction instructions

FYI, this is the same issue I am having, but I do not have this module installed. Also, I do not see this error when logged in as the primary administrator, but when logged in as a mid-level user I get the same error when I try to create a new node. Perhaps that will provide some troubleshooting clues.

Had the same as the op and nearly the same setup.

The error occurred when I wanted the referenced nodes to be sorted by a field (the title) in the edit form.
When I disabled sorting for the referenced nodes (in the node reference field settings), the error went away.

So I assume ``Unknown column 'field_data_title_field0.nid' `` is refering to the referenced nodes titles, not the current nodes title.

Hope it helps someone. It smells like a bug, but I dont feel confident enough to submit a report.

*-pike

I fixed this problem by running update.php

The removal of the ordering from the field settings as outline by #6 did the job for me.

Running update.php did nothing.

Happened to me as well.

Also "solved" it by removal of ordering, but that isn't exactly "solving it".

update.php didn't fix anything.

Some of you may be experiencing #1920998: Unknown Column Error for All Users Except User 1 When Sort Applied To Simple Entity Selection Mode. There is a patch there and it's possible this issue may actually be a duplicate?

I too am having the problem. In my case, I have two content types Game and Team. Each of these has an entity reference to League.

For the entity reference field, field_league I'm using Simple mode with target bundle league and have specified to sort by field_start_date.

When the available options is being built, the query is tagged with both 'node_access" query_TAG_alter() and 'entity_access' query_TAG_alter.

In this query, the only table is field_data_field_start_date and the two query_TAG_alter hooks are mutually exclusive. Both functions are implemented in node.module as

function node_query_node_access_alter(QueryAlterableInterface $query) {
  _node_query_node_access_alter($query, 'node');
}

function node_query_entity_field_access_alter(QueryAlterableInterface $query) {
  _node_query_node_access_alter($query, 'entity');
}

the second parameter to _node_query_node_access_alter() is hard coded and determines which column from the table will be joined with node_access.nid.

Thus I am ending up with field_data_field_start_date.entity_id = na.nid AND field_data_field_start_date.nid = na.nid in different subqueries I believe.

I don't know where the tags are getting added but I don't think we should tagging these sub queries with both entity_access and node_access tags.

1. EntityReference_SelectionHandler_Generic.buildEntityFieldQuery() adds node_access tag to the EntityFieldQuery on league
2. When entity field query is executed, field_sql_storage_field_storage_query() creates a select_query for the field that is being sorted on.
3. field_sql_storage_field_storage_query then calls $query->finishQuery() and passes the select_query to it.
4. EntityFieldQuery.finishQuery() adds all tags from the parent query to the select query. This adds node access in addition to entity_field_access that is already there.

So far my best work around is to change entity.inc from

function finishQuery($select_query, $id_key = 'entity_id') {
    foreach ($this->tags as $tag) {
        $select_query->addTag($tag);
    }
<code>

to

<code>
function finishQuery($select_query, $id_key = 'entity_id') {
    foreach ($this->tags as $tag) {
      if ($tag == 'node_access' && !isset($select_query->alterTags['entity_field_access'])) {
        $select_query->addTag($tag);
      }
    }

I have node idea what kind of issues this may cause or even if the root cause is that EntityReference_SelectionHandler_Generic.buildEntityFieldQuery() is adding "node_access" tag to the query.

I can confirm that the patch referenced in #10 does indeed solve this issue! Thanks for cross posting here as that bug wasn't on my radar.

Patch for #11

My approach was here that the node.module's _node_query_node_access_alter() function has a bad assumption with the field. It assumes that field name to check is "nid" always. But if we use the entityreference module, the referenced field will be entity_id. So, my patch checks if the base_table contains "field_data_" or "field_revision_" string, the referencing field will be entity_id.
I tried to catch the point where I'm able to alter the subquery in the scope of entityreference.module after the node.module adds the wrong query to it, but I wasn't able to do (since both have the same weight in the system table and entityreference's query alter executed earlier).
So, it's not the perfect solution, but it fixed the unknown column issue for me.