>
>
> =>
> => Bconsole already performs SQL queries for all commands that would issue
> a
> => long listing, right?
> =>
> => SQL was meant for filtering & relating data ... Why not add some filter
> => param that is added to the SQL being sent to the backend? something like
> th=
> => e
>
> That's great...if you already know SQL.
>
>
Makes sense, though I hardly think most people would think it's voodoo to
use a limited subset of SQL bits in include / exclude. But i could be wrong.
> I'm guessing that most system administrators who are managing bacula are
> much
> more familiar with shell tools & paradigms than with SQL. I wish I knew
> SQL,
> but even more, I'd prefer to send the output of bconsole to tools that I
> already know (grep, perl, awk, etc.).
>
>
>
How would this integrate with a tool like bat ? ie, it wouldn't allow you to
integrate it easily with bat (for on-the-server processing of the
filtering), would it?
Regards,
____________________
{Beto|Norberto|Numard} Meijome
"I detest people who take shortcuts rather than do things right, because
they leave shit for the rest of us to clean up."
PHK
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
