You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My desired use of sql-metadata is to be able to create an inventory of assets affected by upcoming schema changes.
Originally, I expected the package would create this SET. However, when I call the Parser(self).columns, I see the CTE columns referenced as well. Has anyone created a strategy to separate the CTE columns from table columns?
I am thinking I would exclude columns from the set when the starts_with is not in the Parser(self).tables. Is this the most efficient method others have implemented?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
My desired use of sql-metadata is to be able to create an inventory of assets affected by upcoming schema changes.
Originally, I expected the package would create this SET. However, when I call the Parser(self).columns, I see the CTE columns referenced as well. Has anyone created a strategy to separate the CTE columns from table columns?
I am thinking I would exclude columns from the set when the starts_with is not in the Parser(self).tables. Is this the most efficient method others have implemented?
Beta Was this translation helpful? Give feedback.
All reactions