Original Title was: GEODATABASE_FILE reader to have 1:1 relationship between Tables to read and Where clauses
I frequently want to apply a WHERE clause per Table/Feature Class
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
I'd imagine we'd move to having the where clause be a "feature type parameter" as opposed to the entire reader parameter. Then we could do this nicely.