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
      
      

        Activity

        Hide
        jihoonson Jihoon Son added a comment -

        I have thought about this issue, and want to discuss with other people.
        Do we really need to support multiple columns of the same name in a schema?
        I think that the above example query is hardly used in real applications, because users generally don't want to get the duplicated data.

        Show
        jihoonson Jihoon Son added a comment - I have thought about this issue, and want to discuss with other people. Do we really need to support multiple columns of the same name in a schema? I think that the above example query is hardly used in real applications, because users generally don't want to get the duplicated data.
        Hide
        jihoonson Jihoon Son added a comment -

        I had a talk about this issue with Hyunsik in off-line. In the talk, we agreed on that this issue doesn't need to be solved currently. When a real problem is occured in later, we can reopen and solve this issue.

        Show
        jihoonson Jihoon Son added a comment - I had a talk about this issue with Hyunsik in off-line. In the talk, we agreed on that this issue doesn't need to be solved currently. When a real problem is occured in later, we can reopen and solve this issue.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development