SQL
Editor / Instant SQL View |
The
content assistant can
present tables by schema or catalog since version 1.0.1. Now the tables
from the default schema are also presented if the user you used to
log on the database matches a schema name. Example: If you have pasted a statement like select alpha from beta; into an SQL part where beta is a table that resides in schema gamma, using completion on one of the elements lead to no results. Now, if you logged on the database with user gamma, you can use completion on each of the elements. When content assistance for tables is requested DbEdit now inserts the identifier elements without quotes by default. If you want the quotes because the identifier is a keyword or it must be case sensitive, you can force it by pressing the Shift button. Using the SQL Editor preference page you can also switch back to the previous behaviour. Following a user request the SQL capable parts now support multiline comments using the entry sequence /* and the end sequence */. |
|
|
Table
Editor |
Any
result area used within the Table
Editor or the Instant SQL view now supports fetching a result in chunks
of a variable size.![]() The SQL result parts now support different encodings. To achieve this, DbEdit first converts the strings retrieved from the JDBC driver to the Unicode format and then to the chosen encoding.To select one of the predefined encodings or enter a special one press the third button in the result toolbar. Two new functions have been added to the context menu. Copy as Inserts copies the selected rows as insert statements to the clipboard. Paste Row appends a new row similar to the function Insert Row but the values are prefilled with the content of the clipboard that may be a previously copied row (use Copy Row(s) here). ![]() Please use the Refresh Reference Values button if you want the actual content be filled within the boxes. |
|
|
Tables
View |
A new function in the context
menu when selecting a table element is Copy as DDL, which
copies the create statement that may be used to create the table into
the clipboard. The statement is always a single statement that includes
the table constraint definitions if any. |
|
|
Table Import |
The table import wizard has been reworked as I
noticed
a number of failures. It now separates table structure creation from
the creation of indexes, constraints and the insertion of the values.
Each of the passes that follow the table structure creation can be
disabled. An example where this could be useful is an import of tables
exported from a database that supports constraints into one that
doesn't. |