These specify options relating to the SQL History feature.
There are three history files:
In these cases:
As a result of the last of these items, you may wish to select some of the options below to manage your history file entries.
The name for your history file. If you change this, it comes into effect immediately. This is a simple way of switching to another history file.
This option is useful if you want AQT to use separate history files for a given period. In order to do this, you need to check this option and change your history file name to have a date-period indicator. The date period indicators are: yyyy (year), mm (month), dd (day), ww (week). So:
History File Name |
Effect |
aqt_history_yyyymm.txt |
Separate file each month |
aqt_history_yyyyww.txt |
Separate file each week |
aqt_history_yyyymmdd.txt |
Separate file each day |
AQT determines the filename when it starts - if the day changes during an AQT session, the history filename will not change.
To prevent the history files becoming excessively large, AQT limits the amount of SQL text written with each History record. This option specifies the amount of SQL text written.
By default this is 20000 bytes - you may wish to increase this if you are running large SQL statements and you the full SQL text to be recorded in the History.
The SQL History has a number of options about which SQL statements are included in the history. This is because SQL can be run in many places within AQT:
Run SQL |
These records are always included |
GUI Query Builder |
This includes queries run the Query Builder. An history record is created every time you click on the Run button. |
Table Inline Edit |
This includes the SQL run when you update a table using the Inline Edit feature. |
Row Update |
This includes SQL run using the Row Update / Insert / Delete window. |
SQL Scripts |
By default, when you run a multi-statement script from the Run SQL window, you will get a single history record. When you select this option, you will get an separate history record for every statement run from the Multiple Statements window. |