yourssvk

compare selected does not work properly the first time

2

Steps to reproduce the issue: 1 Launch: https://ec2instances.info/?compare_on=true&selected=c5.4xlarge,m5.4xlarge I would expect the comparison to be done immediately, but I have to press "end compare" and then do a "compare selected"...

sqlalchemy.orm.exc.NoResultFound: No row was found for one()

2

Problem description: If I run detect on a Redshift database with a new catalog db specified for the run, it returns this: piicatcher --catalog-host localhost --catalog-port 5432 --catalog-user piicatcher --catalog-password...

Some name columns are identified as phone pii - unable to ascertain why...

2

Some name columns are identified as phone pii - unable to ascertain why... - it will be good to dump sample values that led to this conclusion somewhere, so that...

shallow scan followed by deep scan causes pk/ uk violations (and possibly viceversa)

2

shallow scan followed by deep scan causes pk/ uk violations (and possibly viceversa)

ERROR: duplicate key value violates unique constraint "unique_column_name" -> This happens on a brand new catalog db on a redshift deep scan, most likely it requires a better unique key...

Seems like the deep scan and the shallow scan are running sequentially, can make parallelism an option, so that the scan can finish way sooner....