Ben Knight
Ben Knight
@johannes-becker-bt The pull currently uses a hash and a random seed as you mention for the exact reason you noted. Using the name of the test does sound like a...
Added an update to resolve #586 as well, I added the update to view name derivation to the unit test materialisations as well.
I do not have permissions to do that, all checks are now passing that the failing tests were updated via #589 so just waiting on @cody-scott to sign it off...
I was following the previous pattern of the macro which took a boolean flag as a string argument, not sure if there was a reason it was done that way.
Looks like other people are seeing the issue and our inability to control the behaviour right now. https://github.com/dbt-labs/dbt-adapters/issues/807
Looks like Fabric adapater went the route of disabling this by default. https://github.com/microsoft/dbt-fabric/issues/255
The simplest method I can think of is to create a custom post hook macro that you pass in the columns you want encrypted along with the details of the...
The issue you have is that DBT will drop and recreate your table so it must know how to encrypt the column when its created, you can't avoid having DBT...
> Additionally, I'm not sure why char_size is twice the string length for nvarchar but I noticed it in my testing which is why I halve it in string_size(). I...
A SQL server specific version of the macro that gets the data seems the safest method to me, as you say it will not be implemented at the Fabric level....