Open jestrickler opened 9 years ago
Would it be really annoying to use SQL change event? ie cause too much work to be done by the client?
I'm not sure if this is a feature or a bug but wondering about what would work best for you while that sorts itself out.
I was thinking of SQL change or adding a listener on column select, but I'm not sure how to get at the tables other than brute force comparing selected columns to metadata to see if an FK was selected.
I think the new visitor stuff should be good for this. Just visit all the tables? I'll have a look/patch to add support for that if that sounds helpful to you?
That does sound like it could be good
Do you have any preference if the visitor visits each table filter in turn or visits a single "from" node and provides a sensible data structure? I think I'm most tempted by the former as it matches visiting lots of nodes in the where clause.
Whichever you think works best. Thanks.
http://savage.net.au/SQL/sql-92.bnf.html I think I will use for the node names/types for visiting.
notes: