-
Is there a way to extract the sql query that represents the (implied?) table of pairs to evaluate for matchy-ness? From error tracebacks (when I've broken stuff) I know it gets computed as part of a CTE during the prediction step, but my ability to reverse engineer things further is limited. Mostly, I'm interested in studying the resulting query since splink overall seems cleverly optimized and I'm hoping it'll teach me something. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
yes - there are a few options:
If you set that after you instantiate the linker, all SQL will be logged In addition, each Splink dataframe has a |
Beta Was this translation helpful? Give feedback.
yes - there are a few options:
If you set that after you instantiate the linker, all SQL will be logged
In addition, each Splink dataframe has a
sql_used_to_create
method and in addition the cache has anexecuted_queries
list self.executed_queries = []