The first thing is something we are planning on enhancing. For now, I suggest that you use the popup before typing "Table1.a". If you have noticed, SQL Assistant parses names of already entered tables and aliases and if you have multiple tables in the same query, it pastes column names as Table.Column, if table names include schema names, it pastes Schema.Table.Column, if tables are aliased, it pastes names as Alias.Column.

As for the handling of local variables, in the current version 1.0 we are trying to avoid full script parsing for performance reasons. Because SQL Assistant is not really part of the editor, it doesn't have access to internal memory buffers used by the editor, and so it basically has to work with the text displayed on the editor screen. Requesting the entire script from the editor and re-parsing it after each change. When large scripts are used, such operations become slow and not very efficient. If you ever worked with SQL Prompt tool you probably know how annoying that is when you have to sit and wait for minutes while your scripts get opened and after various copy and paste operations.

As a side note, we are going to implement some kind of full script parsing in version 2. I don't know if support for local variables will be added in that version.

Regards,
SysOp

Last edited by SysOp on Mon Aug 13, 2007 6:00 pm; edited 1 time in total