Osquery uses basic SQL commands to leverage a relational data-model to describe a device.

osquery

<@U7DT2E8B0> yep, for instance `table_name("carbon_black_info", aliases=["cb_info"])`

It looks like defining a table's name in an extension happens in either the `REGISTER_EXTERNAL` macro or the `addOsqueryExtensionEx` CMake function, but neither seem to support an alias parameter.

But `table_name` even when it's a comma-delimeted list like above, does seem to end up getting passed to `REGISTER_INTERNAL` as `"${ table_name }$"`