The issue was discussed in Slack, and documented here in Confluence.
Summary: While using the wrds module, if the data is in SAS but not in Postgres, the wrds module does not clearly communicate this. For example if using the list_tables method, it throws a NotSubscribedError. Errors messages like these create confusion and this is a common user question on Zendesk. We could do a better job to inform users in the error message(s) that the table being queried does exist, but it only exists in SAS and therefore cannot be accessed using the wrds module.
An ideal solution would reduce user confusion, but also be stable and little effort to maintain.
The issue was discussed in Slack, and documented here in Confluence.
Summary: While using the
wrdsmodule, if the data is in SAS but not in Postgres, thewrdsmodule does not clearly communicate this. For example if using thelist_tablesmethod, it throws aNotSubscribedError. Errors messages like these create confusion and this is a common user question on Zendesk. We could do a better job to inform users in the error message(s) that the table being queried does exist, but it only exists in SAS and therefore cannot be accessed using thewrdsmodule.An ideal solution would reduce user confusion, but also be stable and little effort to maintain.