 |
SoftTree Technologies
Technical Support Forums
|
|
Author |
Message |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
Changes are indeed appear as sticky in the options, but they are more or less cosmetic., they don't alter the behavior of SQL Editor which is specifically designed to recognize database type based on connection details and automatically pick matching SQL Assistance type and the connection specific attributes. If you know how to break that, I mean how to change connection to a different database type and the SQL Editor not following with correct SQL Assistance type and not showing any warnings, please describe the steps. This is an issue that we would like to fix.
|
|
Fri Oct 21, 2016 11:21 am |
|
 |
gemisigo
Joined: 11 Mar 2010 Posts: 2165
|
|
|
|
I guess the assistance is properly set when changing connection types. The auto connection is another question. And we might be afraid about the SQL reference as well. Though I admit, I've never tried to intentionally break those, so it's all theory.
|
|
Fri Oct 21, 2016 6:24 pm |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
One way to mismatch things is to use Ctrl+Shift+F5 while already connected to a database like Oracle, and choose SQL Server Assistance type. That is allowed on purpose, by design. It's there in case things require manual corrections. Another way is to choose a DSN-based ODBC connection to a wrong database. Or select ADO.NET interface with with a wrong server and port. If SQL Assistant detects mismatch between server type and assistance type selected, it shows a warning. But that warning can still be ignored.
|
|
Sat Oct 22, 2016 2:57 am |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|