FluidShell: header for \list command
Can you include header for \list database
For e.g. \list databases
|
55 KB
What is the justification for this? Why is this needed?
I would rather not: currently the code is rather simple, but in order to add this functionality to the \list command it would need to be changed to first load all information into a buffer to compute the column width, then output. Then what about other commands? Why add this feature only to one command?
what about other commands?
I had added another issue for \list tables https://www.aquaclusters.com/app/home/project/public/aquadatastudio/issue/6229?filterQuery=
Why is this needed?
For increased readability for the user and to clone behaviour of other command line tools.
what about other commands?
I had added another issue for \list tables https://www.aquaclusters.com/app/home/project/public/aquadatastudio/issue/6229?filterQuery=
Why is this needed?
For increased readability for the user and to clone behaviour of other command line tools.
No unix shell command provides this functionality.
No unix shell command provides this functionality.
We just need a simple header such as :
Database
------------------
information_schema
aquaclusters
aquadataserver
menagerie
mysql
test
We just need a simple header such as :
Database
------------------
information_schema
aquaclusters
aquadataserver
menagerie
mysql
test
This makes no sense. Please explain why this is needed, what problem is being solved by adding a header.
Will it simplify parsing of the command output?
This makes no sense. Please explain why this is needed, what problem is being solved by adding a header.
Will it simplify parsing of the command output?
A discussion revealed that N. and T. wanted a multi-column output much like the text results, something like that:
|schema |database | |--------|-----------| |dbo |table1 | |dbo |table2 | |schema23|table000000|
What I am suggesting is to add a set of options (TBD) to format the output any way the user may want. If the user wants to get a simple list of tables with no schema and no header, the user should be able to obtain it by supplying specific options on the command line.
I think the tool will benefit if we make it flexible enough that any kind of output is possible, with default options configured to something most frequent (whatever that might be).
I think hard-coding a specific format is less desirable choice.
A discussion revealed that N. and T. wanted a multi-column output much like the text results, something like that:
|schema |database | |--------|-----------| |dbo |table1 | |dbo |table2 | |schema23|table000000|
What I am suggesting is to add a set of options (TBD) to format the output any way the user may want. If the user wants to get a simple list of tables with no schema and no header, the user should be able to obtain it by supplying specific options on the command line.
I think the tool will benefit if we make it flexible enough that any kind of output is possible, with default options configured to something most frequent (whatever that might be).
I think hard-coding a specific format is less desirable choice.
The user may also want to pipe the output to a file or use it somewhere else as an output, and therefore perhaps we neeed to give the user choice of formatting, alignment, delimiter character and so on.
For example:
schema.database
[schema].[database]
etc.
The user may also want to pipe the output to a file or use it somewhere else as an output, and therefore perhaps we neeed to give the user choice of formatting, alignment, delimiter character and so on.
For example:
schema.database
[schema].[database]
etc.
A '-h' option is provided to display output with header(s), header is not shown by default.
> help \list
\list [-h] databases
\list [-d DATABASE] [-h] schemas
\list [-d DATABASE] [-h] [-s SCHEMA] tables
\list [-d DATABASE] [-h] [-s SCHEMA] views
A '-h' option is provided to display output with header(s), header is not shown by default.
> help \list
\list [-h] databases
\list [-d DATABASE] [-h] schemas
\list [-d DATABASE] [-h] [-s SCHEMA] tables
\list [-d DATABASE] [-h] [-s SCHEMA] views
Issue #6228 |
Closed |
Fixed |
Resolved |
Completion |
No due date |
Fixed Build 11.0.0-dev-10 |
No time estimate |
What is the justification for this? Why is this needed?
I would rather not: currently the code is rather simple, but in order to add this functionality to the \list command it would need to be changed to first load all information into a buffer to compute the column width, then output. Then what about other commands? Why add this feature only to one command?