I use Windows XP Pro SP2, SQL 2000 (named instance), English, SQL Query Analyser.
1) in the simple query select * from ... FROM does not trigger the list of tables; CTRL-SPACE does not help either
2) once entering WHERE clause, it presents two lists of columns: the list of columns and the list of columns prefixed with the table name. when using aliases, it presents two lists of tables - the list of columns and the list prefixed with alias. However, if to type the table name or alias and type a period, the list of columns is not present neither CTRL-SPACE is showed up.
3) joins!
I am making next step:
select * from ContactInfo inner join ...
Out of many tables in my database only two views are shown as options - only those which have columns named equal to my primary key. Who made this determination? For this client I have to follow the naming convenction as PK<table name> vs. <table name>FK and not using enforced referential integrity. In many other cases, I use ID as a primary key and <entity>ID as a foreign key. I can join bypassing referential integrity rules as well or use some other fields. I also can have multiple foreign key references from one table to another.
I guess "free" tool in the case of your utility means simply feature prototyping. You shell not make your tool functioning within certain style limits only. The proper intellisense has to support all
syntactically valid cases (and not even bothering us to specify which keywords would trigger lists - unless you allow us specifying different options, behavior or lists depending on each trigger keyword it is up to your syntactical analyser to determine which SQL keyword triggers which possible choices).
1) in the simple query select * from ... FROM does not trigger the list of tables; CTRL-SPACE does not help either
2) once entering WHERE clause, it presents two lists of columns: the list of columns and the list of columns prefixed with the table name. when using aliases, it presents two lists of tables - the list of columns and the list prefixed with alias. However, if to type the table name or alias and type a period, the list of columns is not present neither CTRL-SPACE is showed up.
3) joins!
I am making next step:
select * from ContactInfo inner join ...
Out of many tables in my database only two views are shown as options - only those which have columns named equal to my primary key. Who made this determination? For this client I have to follow the naming convenction as PK<table name> vs. <table name>FK and not using enforced referential integrity. In many other cases, I use ID as a primary key and <entity>ID as a foreign key. I can join bypassing referential integrity rules as well or use some other fields. I also can have multiple foreign key references from one table to another.
I guess "free" tool in the case of your utility means simply feature prototyping. You shell not make your tool functioning within certain style limits only. The proper intellisense has to support all syntactically valid cases (and not even bothering us to specify which keywords would trigger lists - unless you allow us specifying different options, behavior or lists depending on each trigger keyword it is up to your syntactical analyser to determine which SQL keyword triggers which possible choices).