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 | Low |
| Complexity | Unknown |
| Component | App - FluidShell - Command |
| Version | 14.0 |
If Server Connections are not in the default .datastudio\connections folder we get a "No Connection Found: error for runfluidscript command in the command terminal in Windows
To reproduce create a folder under .datastudio and copy your SQL server 2000 server
1. create a new script with below contents
use Northwind
Select count(*) from dbo.Orders @
2. Execute it from the command line
another way is to use the Aqua Data Studio UI to create a mount directory and add the Server to it. See attached screenshot
|
|
41 KB
|
|
43 KB
|
|
47 KB
|
|
59 KB
|
|
22 KB
@funfun: I suspect that the code that processes the "-c" option is always assuming that the data source lives under ".datastudio\connections". If this is the case, then lets introduce a new option in runfluidscript "-m" for mount point. This lets the user specify a different mount point to search under.
> I suspect that the code that processes the "-c" option is always assuming that the data source lives under ".datastudio\connections". If this is the case, then lets introduce a new option in runfluidscript "-m" for mount point. This lets the user specify a different mount point to search under.
This means runfluidscript needs to figure out what is the definition of the 'mount point', i.e. where it points to; not sure how easy this information can be retrieved. If this is what you were asking for, then I will review ADS code next week.
Another alternative is to add an option, e.g. -d, to let user specify a real directory name; if -d is specified, runfluidscript will try to locate the connection file from the specified directory but not the default ~/.datastudio/connections directory. This is much easier to implement.
> I suspect that the code that processes the "-c" option is always assuming that the data source lives under ".datastudio\connections". If this is the case, then lets introduce a new option in runfluidscript "-m" for mount point. This lets the user specify a different mount point to search under.
This means runfluidscript needs to figure out what is the definition of the 'mount point', i.e. where it points to; not sure how easy this information can be retrieved. If this is what you were asking for, then I will review ADS code next week.
Another alternative is to add an option, e.g. -d, to let user specify a real directory name; if -d is specified, runfluidscript will try to locate the connection file from the specified directory but not the default ~/.datastudio/connections directory. This is much easier to implement.
Done:
SVN r36163/14.0.8-12
SVN r36164/15.0.0-dev-118
Done:
SVN r36163/14.0.8-12
SVN r36164/15.0.0-dev-118
If you specify a directory with -d then -c is not optional. Do we need to add in the Usage that if -d is specified then you need to have a connection name ?
If you specify a directory with -d then -c is not optional. Do we need to add in the Usage that if -d is specified then you need to have a connection name ?
> If you specify a directory with -d then -c is not optional. Do we need to add in the Usage that if -d is specified then you need to have a connection name ?
Can you be more specific? This fix will not process the value specified by -d option unless -c option is specified.
> If you specify a directory with -d then -c is not optional. Do we need to add in the Usage that if -d is specified then you need to have a connection name ?
Can you be more specific? This fix will not process the value specified by -d option unless -c option is specified.
Issue #11364 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build 14.0.8-12/15.0.0-dev-118 |
| No time estimate |
1 issue link |
relates to #9155
Issue #9155Fix the "-c" parameter in FluidShell |
@funfun: I suspect that the code that processes the "-c" option is always assuming that the data source lives under ".datastudio\connections". If this is the case, then lets introduce a new option in runfluidscript "-m" for mount point. This lets the user specify a different mount point to search under.