Uploaded image for project: 'Tajo'
  1. Tajo
  2. TAJO-573

Allow the same column in a schema

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: 0.8.0
    • Component/s: Catalog
    • Labels:
      None

      Description

      Recently, I have been working on TAJO-554, and I found that we should allow two or more same columns in a schema to handle the asterisk properly.
      My try in TAJO-554 is rewriting asterisks with their relations' schemas. So, the resulting schema can contain multiple same columns. Here is an example.

      postgres=# select n_name, n_nationkey+10, *, n_regionkey from nation;
      
                n_name           | ?column? | n_nationkey |          n_name           | n_regionkey |                                                     n_comment                                                      | n_regionkey 
      ---------------------------+----------+-------------+---------------------------+-------------+--------------------------------------------------------------------------------------------------------------------+-------------
       ALGERIA                   |       10 |           0 | ALGERIA                   |           0 |  haggle. carefully final deposits detect slyly agai                                                                |           0
       ARGENTINA                 |       11 |           1 | ARGENTINA                 |           1 | al foxes promise slyly according to the regular accounts. bold requests alon                                       |           1
      
      

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              jihoonson Jihoon Son
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: