First off, thanks for the great module. I think it is what I need. I have a very complicated view that uses node references of through about 5 node types. I have a great view set up that utilizes data from most of the nodes but I have an outlying node that has data on it that no matter how I manipulate views with relationships etc, I either get duplicates I can't filter out, or missing data.

This module had appeared to be my savior. That said, I consider myself a beginner in SQL but understand primary keys and foreign keys and basics of MySQL.

Problem is, it's just not working for me. I have Node A and Node B that both Reference Node C and I need to include data from all three. I have to use Node A as the base for the view. I am adding the nid as a primary and the field I need on Node B as a foreign key. I pick automatic and my Node B->field that is keyed just isn't showing up in the view. I tried manual and using relationships and still nothing.

Clearly, I dont' understand and I thought I did. If you have some time between debugging I would be very appreciative for insights on how to get it working. If possible. Thanks a ton.

Comments

moshe weitzman’s picture

moshe weitzman commented
Status: Active » Closed (fixed)

Table wizard does not help with designing Views. It helps write views integration code which a module developer would usually write by hand. Your issue sounds like a support request for the Views project.

tpainton’s picture

tpainton commented

Ah. From the modules main page, "administrators can use Table Wizard to create views of all tables in the database, whether or not their creators provided Views integration." Sounds like a site administrator can use any table in the database to create a view. Might want to clarify that a little better. In addition, the Handbook pages sound like they can be applied directly to the views UI....

"Once added, a table can be used as the base for a view, and a default view of the table is provided (click on the table name in the list). The Analyze page for a table gives you information on the contents of the table (identifying empty fields,
data ranges, etc.) and allows you to identify fields which can be used to join to other tables. You can Reanalyze tables if their contents have changed. Go to Content management => Table Wizard => Relationships to create relationships among the tables you've added to Table Wizard. When you create a relationships between, say, ExampleTbl1.key and ExampleTbl2.key, then in a view containing ExampleTbl1 you can add a relationship to ExampleTbl2, and bring fields from that table into the view."

It all sounds very applicable to view UI. So, maybe this should be documenation clarification?

Sorry about my clutter.

That said, it still might solve my problem if I chose to go the custom module route.