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
When I execute runfluidshell.bat/.sh file, the interpretation of the "-c" parameter is unintuitive and restrictive. The "-c" parameter requires only the connection filename, not the fully qualified path to the connection. Lets say I have the following directory structure:
|---Local Database Server
|--conn1 (.conn file)
|--folderA (folder)
|--conn1 (.conn file)
Problems:
1) To connect to the conn1 under folder A, I cannot type "-cfolderA/conn1". Instead, I must type "-cconn1". This is inconsistent with how the connect parameter works when inside of fluidshell and trying to connect to a given registered server. This also leads to problem #2.
2) This is limiting -- It is not possible for me to connect to conn1. If I type "-cconn1". However, I'll get an error message saying "more than one connection found with the same name." if I have 2 connection files with the same name but in 2 different folders, I'm not able to connect to such a server using the "-c" parameter.
|
|
26 KB
I don't think Sachin's statement is correct, in that fully qualified path doesn't work. Fung, can you verify behavior?
Sachin's statement is correct. See issue #8177 for more information about the explanation of current RunFluidShell behavior.
For \connect command, the current implementation of \connect command requires you to specify the complete path relative to the $CONNECTIONS shell variable:
prompt> \connect Serv2008_7_16/MySQL/MySQL-5.0-Localhost // this works
prompt> \connect MySQL-5.0-Localhost // this won't works
Sachin's statement is correct. See issue #8177 for more information about the explanation of current RunFluidShell behavior.
For \connect command, the current implementation of \connect command requires you to specify the complete path relative to the $CONNECTIONS shell variable:
prompt> \connect Serv2008_7_16/MySQL/MySQL-5.0-Localhost // this works
prompt> \connect MySQL-5.0-Localhost // this won't works
Fixed - SVN r32771/14.0.0-beta-15
The argument specified by -c option now works the same way as \connect command, it should be a complete path that is relative to the 'user.home'/.datastudio/connections folder without the .conn file suffix. Note that this fix is not backward compatible.
Fixed - SVN r32771/14.0.0-beta-15
The argument specified by -c option now works the same way as \connect command, it should be a complete path that is relative to the 'user.home'/.datastudio/connections folder without the .conn file suffix. Note that this fix is not backward compatible.
We should consider how we can provide a fix that is backwards compatible. How about the following options:
Option 1) Introduce a new parameter, -cp (?) that uses the new behavior and don't change the old behavior
Option 2) Modify the "-c" so that it first defaults to the old behavior. If it doesn't find a matching conn, then it uses the new behavior (assumes full path).
Thoughts?
We should consider how we can provide a fix that is backwards compatible. How about the following options:
Option 1) Introduce a new parameter, -cp (?) that uses the new behavior and don't change the old behavior
Option 2) Modify the "-c" so that it first defaults to the old behavior. If it doesn't find a matching conn, then it uses the new behavior (assumes full path).
Thoughts?
I discussed backward compatibility with Niels yesterday before making the changes, Niels said he is not worry about backward compatibility at the moment.
I discussed backward compatibility with Niels yesterday before making the changes, Niels said he is not worry about backward compatibility at the moment.
Fixed: SVN r32777/14.0.0-beta-15. This fix is backward compatible. Discussed with Niels, we will use new implementation (SVN r32771) to locate a connection file by default; if file cannot be found, we then fall back to the old approach.
Fixed: SVN r32777/14.0.0-beta-15. This fix is backward compatible. Discussed with Niels, we will use new implementation (SVN r32771) to locate a connection file by default; if file cannot be found, we then fall back to the old approach.
Issue #9155 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build 14.0.0-beta-15 |
| No time estimate |
3 issue links |
is a duplicate of #8177
Issue #8177Fluid Shell command line -c option |
relates to #11364
Issue #11364"No Connection Found" for a connection not in .datastudio\connections folder for runfluidscript |
duplicates #8177
Issue #8177Fluid Shell command line -c option |
I don't think Sachin's statement is correct, in that fully qualified path doesn't work. Fung, can you verify behavior?