Uh oh!
There was an error while loading. Please reload this page.
PHOENIX-6343 : Phoenix allows duplicate column names when one of them is a primary key - #1117
Conversation
stoty
commented
Jan 28, 2021
💔 -1 overall
This message was automatically generated. |
stoty
commented
Jan 28, 2021
💔 -1 overall
This message was automatically generated. |
stoty
commented
Jan 28, 2021
💔 -1 overall
This message was automatically generated. |
stoty
commented
Jan 28, 2021
💔 -1 overall
This message was automatically generated. |
stoty
commented
Jan 28, 2021
💔 -1 overall
This message was automatically generated. |
ankitsinghal
commented
Jan 29, 2021
having duplicate column names at different hierarchy is not fine? Like below table shouldn't be correct or not allowed? |
stoty
commented
Jan 29, 2021
In your example, how would you address the pk id ? This is the reason that specifically PK and the default cf should not have identical names. |
yes, it makes sense, we can't force users to refer every default cf column with "0." and primary columns directly. Thanks |
virajjasani
commented
Jan 29, 2021
Thanks @ankitsinghal for taking a look. Btw somewhat related discussion happened on #1118 yesterday since I raised both master and backport PRs together. I agree that column with user specified CF should be allowed same column name as pk (or non-pk from different CF) but it's just that allowing the same in default CF makes it bit complicated. |
stoty
commented
Jan 29, 2021
💔 -1 overall
This message was automatically generated. |
stoty
commented
Feb 10, 2021
💔 -1 overall
This message was automatically generated. |
… is a primary key (#1117) Signed-off-by: Geoffrey Jacoby <gjacoby@apache.org>
No description provided.