Hi all,
I've been using CIS for some years now, and it's *great* when set up to query a MariaDB running on linux. (Upwards of 500k parts in the database, but database query is pretty quick).
One thing bugs me though: if I "browse" the database, I can set the appropriate columns, and they'll be saved for the next time I browse that particular database table. But if I "query", then it doesn't matter which table I'm querying, I'll get whatever columns were set up from the last query, even if it was a different table.
Which looks like the "CIS query columns" are set up in capture.ini, and are global for all queries (again, Browsing has per-table setup, so not a problem).
(For example, query in the 'Resistor' table would have things like 'tolerance' and 'tempco'....which are irrelevant for querying the 'BJT' table, while the VCE property should be visible for querying the 'BJT' table but hidden for the 'Resistor' table)
So first a question: is there some way to set up queries so that they'll switch column visiblity, based on the table being queried? (my guess, is NO)
And if not, a feature request: either provide per-table column visibility configuation (just use the 'browse' definitions?) in a file, or provide capability so that the databases can provide the information about which columns should be displayed/hidden.