Easily find issues by searching: #<Issue ID>
Example: #1832
|
|
160 KB
|
|
225 KB
|
|
279 KB
@emil: this is not something we support but can you debug & describe what is occurring wrt the connection.
In the Query Window (QueryPanel) after you execute a query, it will query the connection for the Current Database and set the ComboBox. You can see this in SQL Server or MySQL. We need to make sure we are doing this for MongoJS. This is QueryPanel. QueryPanel will also "cache" the auto-completion meta data, which can be refreshed from the toolbar.
In the Query Window (QueryPanel) after you execute a query, it will query the connection for the Current Database and set the ComboBox. You can see this in SQL Server or MySQL. We need to make sure we are doing this for MongoJS. This is QueryPanel. QueryPanel will also "cache" the auto-completion meta data, which can be refreshed from the toolbar.
We need to make sure we are doing this for MongoJS. This is QueryPanel.
This is already being done as can be tested by using the use <db_name> JS command. Also, by looking in the SQL log & verifying that select @@current_database is executed after any JS EVAL command is submitted.
We need to make sure we are doing this for MongoJS. This is QueryPanel.
This is already being done as can be tested by using the use <db_name> JS command. Also, by looking in the SQL log & verifying that select @@current_database is executed after any JS EVAL command is submitted.
- Patch for mongo-jdbc 1.4.8.2 has been applied in ga-1.
- ADS code has been updated to check if the server context has changed after executing script in MongoJS or MongoSQL Query Analyzer. If the server context has changed, it'll refresh the Database drop-down list and the MongoJS auto-complete configurator.
- When a Query Analyzer window is launched, it is associated with a server registration. The "connect" command doesn't affect the server registration associated with the Query Analyzer window. When you close and then open ADS, the restored Query Analyzer window is associated with the original server registration and the Database drop-down list is populated based on that server registration.
- When launching VA using a result set from the Grid view, VA is associated with the Query Analyzer's server registration. If the result set is from a query after a "connect" command is executed, the "connect" command needs to be included in the query in VA.
db = connect(' ... ');
db.collection.find();
Both of these statements need to be executed together and then launch VA using the result set from the "find" command. Doing a Refresh in VA will then connect to the correct server to fetch the result set.
- Verify this issue using ga-2.
- Patch for mongo-jdbc 1.4.8.2 has been applied in ga-1.
- ADS code has been updated to check if the server context has changed after executing script in MongoJS or MongoSQL Query Analyzer. If the server context has changed, it'll refresh the Database drop-down list and the MongoJS auto-complete configurator.
- When a Query Analyzer window is launched, it is associated with a server registration. The "connect" command doesn't affect the server registration associated with the Query Analyzer window. When you close and then open ADS, the restored Query Analyzer window is associated with the original server registration and the Database drop-down list is populated based on that server registration.
- When launching VA using a result set from the Grid view, VA is associated with the Query Analyzer's server registration. If the result set is from a query after a "connect" command is executed, the "connect" command needs to be included in the query in VA.
db = connect(' ... ');
db.collection.find();
Both of these statements need to be executed together and then launch VA using the result set from the "find" command. Doing a Refresh in VA will then connect to the correct server to fetch the result set.
- Verify this issue using ga-2.
This comment should be logged as a new issue. The problem exists in MongoShell as well & is reproducible in v16. I've logged a new issue for it: 13987
This comment should be logged as a new issue. The problem exists in MongoShell as well & is reproducible in v16. I've logged a new issue for it: 13987
For correct IP address, ADS-17-GA-2 build works properly.
Please refer the screenshot (13949.png)
For correct IP address, ADS-17-GA-2 build works properly.
Please refer the screenshot (13949.png)
Issue #13949 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build ADS 17.0.0-ga-2, mongo-jdbc 1.4.8.2, 2.4.8.0 |
| No time estimate |
@emil: this is not something we support but can you debug & describe what is occurring wrt the connection.