It would be helpful if FunSQL.transliterate would manage two or more contexts. The first context would be core FunSQL, then perhaps PlutoFunSQL, then perhaps a notebook. Currently, it seems identifiers referenced must be pushed all the way upwards, and this makes exporting of Chain needed within PlutoFunSQL even though it's an implementation detail.
It would be helpful if FunSQL.transliterate would manage two or more contexts. The first context would be core FunSQL, then perhaps PlutoFunSQL, then perhaps a notebook. Currently, it seems identifiers referenced must be pushed all the way upwards, and this makes exporting of Chain needed within PlutoFunSQL even though it's an implementation detail.