Closed SemyonSinchenko closed 1 year ago
ID
and id
are reserved column names - we can look at making this configurable if needed but in the current release these are reserved for system use
Best to make it configurable. Or at least raise some exceptions about it on the stage of column adding... Because it is really unobvious to get AnalysisException: Reference 'ID' is ambiguous, could be: ID, ID
. Because ID
is very often usable name. We have such a column in each GDWH table for example. Thank you!
Will add a fix in two phases
id
is added
Expected Behavior
Generation of column with name "ID".
Current Behavior
Exception:
AnalysisException: Reference 'ID' is ambiguous, could be: ID, ID.
Steps to Reproduce (for bugs)
Context
I see that the problem is here And it may be solved by renaming of my column "ID" to "ID_" before generation and then renaming it back after but it looks little creepy for production... Why you cannot use something less frequent usable for inner ID column? Like
datagen__technical__inner__id
for example?Your Environment
dbldatagen
version used: 0.2.0rc1