CREATE TABLE ... LIKE .. INCLUDING PROJECTIONS - auto naming issue
CREATE TABLE ... LIKE .. INCLUDING PROJECTIONS statement is automatically copying the projections from the source table. At the same time the replicated projections are named automatically. Every time this statement is done, the output projection names become longer and longer like for example below:
# iteration, source table proj name, target table proj name
1,dg_tables2_b1, dg_tables2_v1_b0
2,dg_tables2_v1_b0, dg_tables2_v1_v1_b0
3,dg_tables2_v1_v1_b0, dg_tables2_v1_v1_v1_b0
So every time the statement is executed Vertica adds the 'v1_' into the projection name. At the end the projection names becomes very long, sooner or later I will hit the 128 chars limit.
Do you know how to control this Vertica projection auto naming to avoid this 'v1_' to be added?
# iteration, source table proj name, target table proj name
1,dg_tables2_b1, dg_tables2_v1_b0
2,dg_tables2_v1_b0, dg_tables2_v1_v1_b0
3,dg_tables2_v1_v1_b0, dg_tables2_v1_v1_v1_b0
So every time the statement is executed Vertica adds the 'v1_' into the projection name. At the end the projection names becomes very long, sooner or later I will hit the 128 chars limit.
Do you know how to control this Vertica projection auto naming to avoid this 'v1_' to be added?
0
Comments
Can you let us know the exact vertica version and exact create table command you are executing.
Regards,
Shobhit
The exact SQL command: create table dg_tables2 like dg_tables including projections;