Should KeyTable get global fields?

I think yes. This is an open issue, as well (

I think there’s actually not really a discussion here.

1 Like

OK, I’m starting to think about how to implement this. The most straightforward way would be to change the current keytable expr interface to access fields through row.field instead of just field. The eval context will have two fields, row and globals, instead of being set for every row. This will also significantly improve the performance of all keytable expr in the short term (until EvalContext goes away).

Any problems with this @cseed? I don’t want to do a bunch of work for nothing.