Closed (fixed)
Project:
Table Wizard
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
29 Nov 2009 at 12:37 UTC
Updated:
7 Feb 2010 at 19:10 UTC
How do I create a relationship between an "external" content (with NID field) and standard nodes ?
Is there a way to create a view that include both ?
All I saw is a way to create relationship between two external tables.
I don't want to migrate content - I want to keep using the external table, which already "sync" with standard nodes, only without Views...
Hope I was clear enough with my question.
Regards,
Shushu
Comments
Comment #1
mikeryanIt should be possible to add the node table to Table Wizard, then add a relationship to that, but this seems to be broken at the moment. I will investigate...
Comment #2
frankcarey commentedjust a hint: i think i noticed this from last dev version where "existing" views tables didn't show up.
Comment #3
mikeryanOK, it's a little better, but not perfect - manual relationships from another table to node seem to work fine, automatic relationships are a bit flaky (only the nid shows up by default, and other node fields show Array() in the views UI where they should show Node).
Comment #4
frankcarey commentedI just came across this issue as well. The problem is that tw is naming the internal tables inconsistently (at least with map tables).
This is what I get when I export the definitions from TW. So, I think we need to either made sure that TW uses db.table all the time, or consistently doesn't use it for default tables. I vote for consistently just using the table name for default tables.
Comment #5
frankcarey commentedtw_qualified_tablename still needs some love, but this will at least get it to only use the database for external tables only. I changed:
Here is how I have it in my dev version.
Comment #6
mikeryanFixed - group field was getting messed up.