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
Our SQL breadcrumbs land a pretty heavy hammer on the SQL query content by removing almost everything except SQL keywords. This leads to less than useful breadcrumbs. Perhaps we can do better.
I am thinking we could introduce a new config option that allows a user to specify a less restrictive SQL obfuscator class. One that can keep table & field names. We can then default to the more restrictive obfuscator for a while and if there are no issues with testing we can default to the less restrictive class after.
This could also allow users to create their own obfuscator class that lets them not obfuscate at all if they are not worried about leaking sensitive data.
The text was updated successfully, but these errors were encountered:
Our SQL breadcrumbs land a pretty heavy hammer on the SQL query content by removing almost everything except SQL keywords. This leads to less than useful breadcrumbs. Perhaps we can do better.
I am thinking we could introduce a new config option that allows a user to specify a less restrictive SQL obfuscator class. One that can keep table & field names. We can then default to the more restrictive obfuscator for a while and if there are no issues with testing we can default to the less restrictive class after.
This could also allow users to create their own obfuscator class that lets them not obfuscate at all if they are not worried about leaking sensitive data.
The text was updated successfully, but these errors were encountered: