|
<< Click to Display Table of Contents >> SQL statement auto storage |
  
|
|
<< Click to Display Table of Contents >> SQL statement auto storage |
|
Content of each tab is auto-saved as per user stored in the INI file following the location of the AbsoluteSQL application using the current Windows user name as the INI section heading. To comply with the single line keys nature of the INI files line breaks are substituted by the '<br>' character sequence indicating line breaks.
If running the application from a removable device, the "user" section as stored on the removable will be [REMOVABLE], thus not dependent on the current user name on the PC currently running the application from the removable.
Due to the inherent limitations of 2058 characters for string lengths in an INI file, long SQL statements are broken up into sections, and SQL statements are auto-stored only up to a total of well over 8000 characters, 8188 including formatting characters.
Truncating auto stored very long SQL statements will be warned as:
However, SQL statements of any size may by manually stored and retrieved via the SQL Menu to/from storage folder of choice.
See Open SQL / Save SQL menus.
As the SQL auto save relies on storing into the INI-file, data contents (from INSERT INTO ... VALUES ...) will always limit to the current system reading of the ANSI character code set.
To store mixed language UNICODE characters, you should use manual [SQL Save ...] saving into individual *.sql files.
On application launch auto stored SQL statements are automatically reloaded from the INI file and reassembled to the non broken SQL statements loaded into the SQL statements tabs.
As the tabbed SQL statements are stored in the application INI-file, do remember to copy and bring along the INI-file, if you relocate your application exe.
As the INI-file on a network file server will be shared by users using the application, never delete or remove the INI-file if it holds data from other users.
__________________________