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
For instance, I'm trying to connect to database x which is buried under 3 nested folder "F1 / F2 / F3 / ServerName1 / DB_x". When I drag & drop database "x" from "Servers" tab into FS, FS should print out: "F1 / F2 / F3 / ServerName1 / DB_x"
If I drag & drop ServerName1, then FS should print out: "F1 / F2 / F3 / ServerName1"
In the current implementation, one can select a list of tree nodes (any tree node) from the schema tree and then drag-N-drop the selected nodes to FS; the result is a list of object names separated by comma. This feature request seems to ask for a customization for some specific tree nodes, is this correct? If yes, can you provide the list node types that need to be customized?
This feature request seems to ask for a customization for some specific tree nodes, is this correct?
Yes
can you provide the list node types that need to be customized?
The DB Server Registration tree node. If that is drag-n-drop'd, then the full path should be inserted. "Full path" means folder hierarchy and the DB Server name. e.g. "folder1/folder2/folder3/DB_Server_Name"
Use case to validate: connect <drag-n-drop DB Server tree node>
This feature request seems to ask for a customization for some specific tree nodes, is this correct?
Yes
can you provide the list node types that need to be customized?
The DB Server Registration tree node. If that is drag-n-drop'd, then the full path should be inserted. "Full path" means folder hierarchy and the DB Server name. e.g. "folder1/folder2/folder3/DB_Server_Name"
Use case to validate: connect <drag-n-drop DB Server tree node>
Made change so that drag-n-drop a DB Server node from Servers explorer to FS would provide a path that can be used by \connect command. Now one should be able to do something like:
> \connect <drag-n-drop DB Server node>
or
> \connect <drag-n-drop DB Server node> -d <drag-n-drop a Database node>
Note that Projects explorer also can have a DB Server node, drag-n-drop a DB Server node from Projects explorer to FS only generates the server name.
Made change so that drag-n-drop a DB Server node from Servers explorer to FS would provide a path that can be used by \connect command. Now one should be able to do something like:
> \connect <drag-n-drop DB Server node>
or
> \connect <drag-n-drop DB Server node> -d <drag-n-drop a Database node>
Note that Projects explorer also can have a DB Server node, drag-n-drop a DB Server node from Projects explorer to FS only generates the server name.
Issue #7824 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build trunk/29885 |
| No time estimate |
In the current implementation, one can select a list of tree nodes (any tree node) from the schema tree and then drag-N-drop the selected nodes to FS; the result is a list of object names separated by comma. This feature request seems to ask for a customization for some specific tree nodes, is this correct? If yes, can you provide the list node types that need to be customized?