<table_ref>

It is an XML parsing error if any child <relationship> from the referenced global table has a child <table> with an id value matching any <table> id of a <table_ref>'s <relationship>s. The error occurs because child <relationship> <table>s of the same parent must have identical <table> ids in order to keep table resource path unique.

This means the following Pull Reports™ XML Catalog file will error when parsed:

<?xml version="1.0" encoding="UTF-8"?>
<catalog xmlns="http://www.pullreports.com/catalog-1.7.0" id="id" name="name">
    <report id="test" name="Test">
        <table_ref id="details" displayName="Details" ref="global">
            <relationship>
                <join_table name="foo_bar">
                    <join_columns><join_column columnName="details_id" referencedColumnName="id" /></join_columns>
                    <inverse_join_columns><join_column columnName="same_id" referencedColumnName="id" /></inverse_join_columns>
                </join_table>
                <table id="same" displayName="Same" name="same">
                    <column id="id" name="id" displayName="ID"/> 
                </table>
            </relationship>
        </table_ref>
    </report>
    <table id="global" displayName="Global" name="global">
        <column id="details_id" name="id" displayName="ID"/> 
        <relationship>
            <join_table name="foo_bar2">
                <join_columns><join_column columnName="details_id" referencedColumnName="d" /></join_columns>
                <inverse_join_columns><join_column columnName="same_2_id" referencedColumnName="id" /></inverse_join_columns>
            </join_table>
            <!--  Invalid: Even though the two relationship tables reference database tables with different names, 
                  "same" vs "same_2", the fact that the <table> id attributes are both "same" causes an error. -->
            <table id="same" displayName="Same" name="same_2">
                <column id="id" name="id" displayName="ID"/> 
            </table>
        </relationship>
    </table>
</catalog>

A global table <table> that contains <table_ref> to itself within a nested <relationship> element creates a join tree that recurses to infinite size. Pull Reports™ detects this recursion and stops the join tree relationship nesting on the second instance of a global <table>.

This means that if global table A has a <relationship> child <table> B, and <table> B in turn has a <relationship> child which <table_ref> references back to global <table> A, Pull Reports™ will prevent the second, nested table A from having relationship children. This effectively stops the join tree at path /A/B/A instead of permitting the infinitely recursive /A/B/A/B/... join tree path.

Specifies the id of the <table_ref> within table resource path statements.

All <table>s and <table_ref>s nested within <relationship>s with the same <table> join parent must have unique id values between themselves. This requirement ensures that each table resource path uniquely identifies one <table> or <table_ref> within a <report>.

The human-readable name. If not specified, uses the displayName attribute of the referenced global <table>.

Specifies the id of the referenced global <table>.