Integrity constraint violation: 1052 Column 'uid' in field list is ambiguous

Can you please export the view?

In general this looks like a problem of the flag module in d7.

Can you please provide a flag export, too?

To be able to fix this bug it's required to reproduce the bug :)
Alternative a feature (from the features module) is required.

Can you test whether this still happens with the latest version of views (dev) ?

There was a lot of fixes recently.

hadsie,
I installed your feature, what do I have to do to replicate the error? Please provide step by step instructions.

subscribing,

I think I have similar issue.

1) I created a new type of content - an meeting,
2) I created a a flag "i'll be there" so an user can confirm that he/she will be attending,
3) I created a view "who flagged a node", with relationship between nodes and users, with id of node as argument,
4) When I add "user name" and "user email" - everything works perfect - I get names and mails of users who flagged a meeting.
5) when I add "bio" or any other field that I created in users - I receive 0 results. Sometimes I receive an strange error - nearly a blank page with whole view definition in one very long line.

The replication is really the main thing here. Without a reproducable bug it's impossible to fix this, perhaps, existing bug.

Here it would also help if you could enable display of php errors

Getting this with the latest dev on a comment view using relationship comment:content and comment:user.

Error message: SQLSTATE[23000]: Integrity constraint violation: 1052 Column 'uid' in field list is ambiguous

See attached view

Pretty obvious problem in the query:

SELECT users_comment.name AS users_comment_name, users_comment.uid AS users_comment_uid, comment.created AS comment_created, node_comment.title AS node_comment_title, node_comment.nid AS node_comment_nid, picture AS picture, uid AS uid, name AS name, mail AS mail
FROM 
{comment} comment
INNER JOIN {users} users_comment ON comment.uid = users_comment.uid
INNER JOIN {node} node_comment ON comment.nid = node_comment.nid
WHERE (( (comment.status <> '0') AND (node_comment.status = '1') ))
ORDER BY comment_created DESC
LIMIT 10 OFFSET 0

While I don't know why this happened, the problem is here:

/* Field: User: Picture */
$handler->display->display_options['fields']['picture']['id'] = 'picture';
$handler->display->display_options['fields']['picture']['table'] = 'users';
$handler->display->display_options['fields']['picture']['field'] = 'picture';

That field does not have a relationship, meaning it's trying to work from the base relationship. It *should* be auto-adjusting to use the user relationship, but maybe somehow that's failing. Edit the view, edit that field, and ensure it's selecting the correct relationship. Then choose 'update' on that field (Regardless of whether it appeared to have the correct value or not) and try previewing the view to see if the query is updated.

If that doesn't, check all of the user: fields for the same thing.

Ah.. that did work. Good call. I wonder why the relationship wasn't automatically selected (like the other fields were).

Thanks

That part seems like it is still a bug and should be explored.

For example, can you create a new view similarly and still have this problem?

hm.. can't seem to get it to happen again.

Seems like a duplicate of #1309142: SQLSTATE[23000]: Integrity constraint violation: 1052 Column 'vid' in field list is ambiguous (or the other way around, but that issue is more generic and has more information)?