Add a command-line switch to either tbls out or tbls lint to ignore virtual information about tbls

[mjpieters]

So far, tbls doesn't assume use case to read the same .tbls.yml twice.

Ah, see, this was the key. Not using a tbls.yml file on the remote machine produces a larger JSON file (as the ignored tables are included now), but also doesn't add virtual tables.

So, updating my ssh alias to:

alias rtbls="ssh server 'tbls out postgres://user@localhost/dbname -t json' > /tmp/tbls.json"
rtbls && tbls lint json:///tmp/tbls.json

works without having to strip virtual relationships. I guess I can live with that.

[k1LoW]

Hi @mjpieters ! Thank you for your report.

Probably adding "virtual relations" in duplicate.

1. execute rtbls and get tbls.json, using .tbls.yml = Add virtual relations
2. execute tbls lint json:///tmp/tbls.json using .tbls.yml = Add virtual relations

Unfortunately the above behavior is by design

[mjpieters]

Yes, that's what I feared, the virtual relations being added twice, first when exporting with tbls out -t json, then again when linting.

Would it make sense to add a command-line switch to either tbls out or tbls lint to ignore virtual information, so I can handle this explicitly?

For now, the jq filter works for my use case.

[k1LoW]

Yes, that's what I feared, the virtual relations being added twice, first when exporting with tbls out -t json, then again when linting.

So far, tbls doesn't assume use case to read the same .tbls.yml twice.

Would it make sense to add a command-line switch to either tbls out or tbls lint to ignore virtual information, so I can handle this explicitly?

fmfm... Could you provide any other use case please? (I’ll consider it.)