You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm looking for a way to track table dependencies and the various watchedTables implementations look to be exactly what I'm after. Alas I can't seem to find a uniform interface for all selectables. I've hacked together a hodge-podge of functions that branch based on types, but if this is something that would be of interest to the project then I'd be happy to contribute something - in which case the PR is a request for guidance on API.
Alternatively a uniform interface for selectables to generate GenerationContexts would also suffice.
What's your use case of going from Selectable -> GenerationContext? Is this only to extract watched tables? We aren't using GenerationContext everywhere (it's not used for custom queries, for instance), but I'm thinking about adding an interface to represent built statements in the next drift version. We could make that available from Selectables.
What's your use case of going from Selectable -> GenerationContext? Is this only to extract watched tables?
Purely as a way to get watched tables, yes. I only mention this because I thought the deprecated implementation indicated this might be the direction things are heading in.
I'm looking for a way to track table dependencies and the various
watchedTables
implementations look to be exactly what I'm after. Alas I can't seem to find a uniform interface for all selectables. I've hacked together a hodge-podge of functions that branch based on types, but if this is something that would be of interest to the project then I'd be happy to contribute something - in which case the PR is a request for guidance on API.Current implementations:
Alternatively a uniform interface for selectables to generate
GenerationContext
s would also suffice.The text was updated successfully, but these errors were encountered: