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
If we have a query in the query builder which queries tables from multiple databases, then the Execute Edit will fail. If you take the SQL and put in a Query Window and execute edit, then it will succeed. The table extraction for execute edit in the query builder seems to assume that both both tables are always in the same database, which is not correct. We need to make the query builder behavior similar to the query window behavior.
See attached example.
Hi Asif, I checked in a fix for this in v18 - svn #46275. I tested it with Niels scenario and several others across different databases. It looks like it is working ok. Please do a code review and make any changes if necessary. I will check it into v16 and v17 tomorrow for QA guys to test. Thanks in advance, Tom
svn #46275
Tom, I have made following changes in US Trunk (SVN r46283):
-- change database first and then the schema
-- I do not see a need for computing whether the schema is case sensitive; by default we always assume it is case sensitive.
I just tested the cross database/schema query against SQL Server and Oracle; you may want to try some more databases.
svn #46275
Tom, I have made following changes in US Trunk (SVN r46283):
-- change database first and then the schema
-- I do not see a need for computing whether the schema is case sensitive; by default we always assume it is case sensitive.
I just tested the cross database/schema query against SQL Server and Oracle; you may want to try some more databases.
Issue #13772 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build ADS 16.0.9-1 |
| No time estimate |
Hi Asif, I checked in a fix for this in v18 - svn #46275. I tested it with Niels scenario and several others across different databases. It looks like it is working ok. Please do a code review and make any changes if necessary. I will check it into v16 and v17 tomorrow for QA guys to test. Thanks in advance, Tom