These are a number of miscellaneous options controlling how data is displayed.
This is a technical option concerning the way AQT uses the grid.
When this option is selected, the columns in the grid will be defined as per the data type of the data being displayed:
In most cases, this will display the data correctly. However there are some possible problems:
When this option is not selected, all grid-columns will be defined as character. The data will display more accurately, however:
By default this option is selected. If you have a problem with the display of numeric columns, you should switch this option off.
This is similar to the previous option, but this is only done for Date and Time columns.
This allows you display Date and Time columns as character, but display columns of other types normally. You would do this by selecting Use Correct Data Types for Grid Columns and also selecting this option.
Note: this option only applies to columns defined as Date or Time. Many databases do not have a Date and Time data type but store date and time values in a datetime or timestamp data type. This option does not apply to these, as these datatypes will be displayed by AQT in a character grid column.
Normally, numeric columns are displayed in a grid column defined as Decimal. In some circumstances this cannot display particularly large values. To deal with this, this option can be selected; in this case numeric columns will be displayed in a grid column defined as Double. This can handle virtually all numeric values, however there can be loss of some precision digits for large values.
This option is useful for databases that have an internal table row identifier that can be displayed with the contents of the table.
When this option is selected, this rowid is displayed when a table is displayed. AQT does this by changing the table-display SQL to include the rowid column.
You may notice that this option doesn't come into effect right away - only on the next table you display.
Displaying the rowid is often useful when you wish to edit the data in a table. AQT will recognise the rowid column as a valid table key, and will use this to identify the rows you are updating or deleting.
This is a potentially useful option for database developers. When a value is inserted into a Varchar column the length of the column has to be set (in C and Java this is generally done with the null byte, in other languages a length field is set). When you display the table you can verify that the data has been loaded correctly, however the column length cannot be seen.
When you select this option the length of the column is displayed, along with the data. For instance
FRED will be displayed as
(4)FRED. This can be useful for verifying that the column lengths have been set correctly - if instead you see
(20)FRED then you know that you are filling your database up with a lot of unnecessary blanks! This has happened on some projects we have been involved in.
When this option is selected (which is the default), AQT removes spaces from the end of string values. De-select this option if you wish to retain these spaces.
This option is used when displaying data, plus the following AQT features:
When this option is selected and you are displaying a DB2 iSeries physical / logical, AQT will use the Column Headers (rather than the Column Name) when displaying the table contents.
If the Column Heading is blank, AQT will use the Column Text.
Most versions of the Oracle ODBC Driver do not handle Timestamp or Interval columns. When you try to display these, the ODBC Driver, and AQT, will crash. AQT has a work-around for this problem; when you display a table with columns of these types, and you have this option selected, AQT will enclose the timestamp/interval columns in a TO_CHAR function.
By default, this option is selected. De-select this option if you have a recent version of the Oracle ODBC Driver that can display these data types without problem/