Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA |
|
| Priority | Minor |
| Complexity | Unknown |
| Component | App - FluidShell |
| Version | 12.0 |
When I enter session, I see output as below:
ID Status User Database Server -------- --------- ------------ ------------ ------------------------------------- default* Connected aquaclusters acmigr_test2 /home/s/.datastudio/connections/local
Notice the value of "Server" -- it is a fully qualified path on my hard drive. However, when I use the "connect" command to connect to a server, I don't specify a fully qualified path. I specify "Folderx../DB_Server_Name". I suggest that the session command should display "Folderx../DB Server Name" instead of the fully qualified path on my hard drive.
This sounds like a good idea. But we may also want to add an option to session like "-d" which will print the value of the CONNECTIONS shell variable, so "session -d" would print :
$:1> session -d Connections Folder : /home/nnn/.datastudio/connections ID Status User Database Server -------- --------- ---- --------- ---------------- default* Connected sa Northwind /MS2000
Made change so that 'Server' column will display a relative path if the connection folder is the parent of the corresponding server file; otherwise, an absolute path is displayed.
If an ID argument is supplied then -d option cannot be used, a warning message will be displayed:
> \session -d -c ID
> \session -d ID
-d option only valid when executing \session as
> \session -d
See man page for more info. Not sure why -d option is desired, 'Connection Folder:' could always be displayed when listing sessions.
The 'Connection Folder:' will show 'Undefined' if CONNECTIONS shell variable is undefined.
*** Note on CONNECTIONS variable ***
One thing we need to review is what does it mean if one set CONNECTIONS to a relative path:
> declare CONNECTIONS=a_relative_path
Does it mean a path relative to the working directory, or something else? In the current implementation, shell will use the directory where ADS is launched as the parent directory for a_relative_path.
Made change so that 'Server' column will display a relative path if the connection folder is the parent of the corresponding server file; otherwise, an absolute path is displayed.
If an ID argument is supplied then -d option cannot be used, a warning message will be displayed:
> \session -d -c ID
> \session -d ID
-d option only valid when executing \session as
> \session -d
See man page for more info. Not sure why -d option is desired, 'Connection Folder:' could always be displayed when listing sessions.
The 'Connection Folder:' will show 'Undefined' if CONNECTIONS shell variable is undefined.
*** Note on CONNECTIONS variable ***
One thing we need to review is what does it mean if one set CONNECTIONS to a relative path:
> declare CONNECTIONS=a_relative_path
Does it mean a path relative to the working directory, or something else? In the current implementation, shell will use the directory where ADS is launched as the parent directory for a_relative_path.
Issue #7848 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build trunk/29922 |
| No time estimate |
This sounds like a good idea. But we may also want to add an option to session like "-d" which will print the value of the CONNECTIONS shell variable, so "session -d" would print :