Frank Oosterhuis
Frank Oosterhuis
But the 1001 user comes from the docker plugin right? If not, you might be right :)
I don't really like any of the solutions, but I'm not sure there is a better way 🤷
I have the same. Looks like the columns that do not have a macro are being pushed back for some reason
It's very slow for me on the Windows drive in WSL2. A native checkout in WSL2 is very quick to assemble.
Interesting... at least the documentation is ambiguous then :)
Probably stating the obvious, but can confirm this is also present in 1.8.3
There is actual code to make sure the not_null is applied first: https://github.com/databricks/dbt-databricks/blob/ec63dce4ff287756ce1821d4f6d2f36b756fb8b2/dbt/include/databricks/macros/relations/constraints.sql#L82 I _think_ it sorts by alphabet so that not_null comes before primary_key 🤐 Main problem for this...