View integration : needs a relationship in the user based views

I agree this could be a great addition, but I don't know out the top of my head how to implement this. Since an user can have multiple addresses, we have a one to many relationship here. Do you know other modules with a one to many relationship with which you can set a relationship on user based views? If so, I could use that as an example and then I would be able to implement this sooner. Maybe the modules Profile 2 or Content Profile?

Thanks. I've looked into the Webforms code and also in Ubercart Views code and saw two possible ways to implement it.
The first implementation (example taken from Ubercart Views) exposes the fields of Ubercart Addresses directly without needing to add a relationship in Views first.
For the second implementation (example taken from Webform), a relationship needs to be added before the fields from Ubercart Addresses will become available. I didn't manage to get this implementation to work with Views 6.x-2.x, so I think it works with Views 3 only.

So, I think it's best to take implementation #1 for the 6.x-2.x version and implementation #2 for the 7.x-1.x version.

Here is a patch for the 6.x-2.x version.

Oops, forgot to post the two different implementations here.

Implementation #1:
Address fields are directly available.

$data['uc_addresses']['table']['join']['users'] = array(
  'left_field' => 'uid',
  'field' => 'uid',
);

Implementation #2:
A relationship needs to be added before the address field are available. Works with Views 3, but not with Views 2.

$data['users']['uc_addresses'] = array(
  'title' => t('Ubercart addresses address'),
  'help' => t('Addresses of the given user.'),
  'real field' => 'uid',
  'relationship' => array(
    'base' => 'uc_addresses',
    'base field' => 'uid',
    'handler' => 'views_handler_relationship',
    'label' => t('Ubercart addresses address'),
  ),
);

True that it may be simpler to get the fields directly, but it could also possibly lead to confusion when you would make a complex View (for example with using reference fields): to which data this address belongs? I think the second implementation is more explicit.

By the way, did the patch work for you? Did you miss something? Let me know!

Thanks for spotting the missing info about country and zone information! After a bit of puzzling, I manage to add them. I had to explicitly setup a new 'join' from the uc_countries table to the user table, with using 'uc_addresses' as the 'left_table'.

Let me know if this works for you or if something still misses.

Thanks for reporting back! Committed #9.

Needs porting to the 7.x-1.x version.

Patch for the 7.x-1.x version. This implementation requires you to add a relationship in your user based View before the address fields will become available. Apparently, using this approach, the country and zone fields remain: I don't need to give Views extra instructions to expose them again as was the case in the implementation for the 6.x-2.x version (see #9). Note: the 6.x-2.x implementation is still fine as the implementation used for the 7.x-1.x version doesn't seem to work properly with Views 6.x-2.x (as noted in #4).

Committed #12.