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 right click on a collection, we should apply the following logic to the Script Object options:
We should detect if the current query analyzer window is MongoJS or not. If MongoJS, we should script as MongoJS instead of MongoSQL. We could even change the cascading menu items FIND, ...
SCRIPT OBJECT TO NEW WINDOWS AS
We should detect if the default is set to MongoJS or MongoSQL. If MongoJS, then generate MongoJS script
SCRIPT OBJECT TO FILE AS
We should detect if the default is set to MongoJS or MongoSQL. If MongoJS, then generate MongoJS script
Some MongoSQL commands might not have direct MongoJS equivalents. We might skip those. The most important ones are related to SELECT, then Ins/Upd/Del. We could skip the DDL ones.
The scripting implementation is complete and working for select*, select, insert, update, delete. Do we want to do the DDLs as well or skip?
Controlling the tree nodes menu conditionally by determining which window is the current active target is not done. We should file a separate issue for that if we want that implemented, will probably take a bit of work to implement correctly.
The scripting implementation is complete and working for select*, select, insert, update, delete. Do we want to do the DDLs as well or skip?
Controlling the tree nodes menu conditionally by determining which window is the current active target is not done. We should file a separate issue for that if we want that implemented, will probably take a bit of work to implement correctly.
Controlling the tree nodes menu conditionally by determining which window is the current active target is not done. We should file a separate issue for that if we want that implemented, will probably take a bit of work to implement correctly.
Pls log as a separate issue and assign to me -- version 18
Controlling the tree nodes menu conditionally by determining which window is the current active target is not done. We should file a separate issue for that if we want that implemented, will probably take a bit of work to implement correctly.
Pls log as a separate issue and assign to me -- version 18
The scripting implementation is complete and working for select*, select, insert, update, delete. Do we want to do the DDLs as well or skip?
Lets first fix the following issues:
1) If choose Script Object to File a file dialog opens w/ and the File Format is specified as SQL Scripts. This is incorrect for MongoJS. Instead, the File Format options should read: JavaScript - ... Jenny has already made this code change when you are in a MongoJS Query Analyzer window & you click on "Save Query" icon. You should use the same set of file formats as displayed in that dialog.
2) Scenario:
- default Mongo syntax is MongoJS
- MySQL Query Analyzer tab has focus
- In schema browser, I right click on the Mongo collection & choose Script Object to Window, the SQL generated should be in MongoSQL not MongoJS.
3) DDLs: if you can get this done in approx a couple of hours, then yes go ahead & implement it.
The scripting implementation is complete and working for select*, select, insert, update, delete. Do we want to do the DDLs as well or skip?
Lets first fix the following issues:
1) If choose Script Object to File a file dialog opens w/ and the File Format is specified as SQL Scripts. This is incorrect for MongoJS. Instead, the File Format options should read: JavaScript - ... Jenny has already made this code change when you are in a MongoJS Query Analyzer window & you click on "Save Query" icon. You should use the same set of file formats as displayed in that dialog.
2) Scenario:
- default Mongo syntax is MongoJS
- MySQL Query Analyzer tab has focus
- In schema browser, I right click on the Mongo collection & choose Script Object to Window, the SQL generated should be in MongoSQL not MongoJS.
3) DDLs: if you can get this done in approx a couple of hours, then yes go ahead & implement it.
Fixed the following scenario. Please re-verify this issue.
1. Set File -> Options -> Query Analyzer -> MongoDB -> Default Syntax -> MongoJS
2. Select a collection node for MongoDB and bring up the pop-up menu
3. Choose one of the following "Script Object to File As" options:
- CREATE
- CREATE (Full)
- ALTER
- DROP
4. Even though JS script is generated, the script is saved to a .sql file. It should be saved to a .js file.
Fixed the following scenario. Please re-verify this issue.
1. Set File -> Options -> Query Analyzer -> MongoDB -> Default Syntax -> MongoJS
2. Select a collection node for MongoDB and bring up the pop-up menu
3. Choose one of the following "Script Object to File As" options:
- CREATE
- CREATE (Full)
- ALTER
- DROP
4. Even though JS script is generated, the script is saved to a .sql file. It should be saved to a .js file.
Issue #13525 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build ADS 17.0.0-ga-5 |
| No time estimate |
Some MongoSQL commands might not have direct MongoJS equivalents. We might skip those. The most important ones are related to SELECT, then Ins/Upd/Del. We could skip the DDL ones.