Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Discussion options

I see that the Non-Standard Blank Values Anomaly is sometimes too sensitive. I have a column of type BIGINT that has an incrementing ID in it. The Non-Standard Blank Values test is picking up 99, 999, 999999, 9999999 as being Blank Values. It's simple enough to Mute the Anomaly, but a nice to have is to not flag it in the first place. The values in the column are 100% filled and mostly continuous.

You must be logged in to vote

Replies: 3 comments

Comment options

I found a similar, but different example: I have distinct values in my column: 00, 01, all the way up to 12, but the 00 is getting flagged as a NSBV.

You must be logged in to vote
0 replies
Comment options

Yeah, I agree 99%. What functional data type are you getting for those columns? This might help distinguish valid values.

You must be logged in to vote
0 replies
Comment options

For the first example, The physical table is VARCHAR(100) (Dataype Suggestion is the same). The Functional Data Type is 'ID-Unique'.

For the seconds one,
Physical: varchar(100)
Datatype Suggestion: INTEGER
Functional Data Type: UNKNOWN

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
💡
Ideas
Labels
None yet
2 participants
Morty Proxy This is a proxified and sanitized view of the page, visit original site.