How can we help you today? How can we help you today?
jonathan.lee
Activity overview Badges (0) Posts (1) Comments (2)

Activity overview

Latest activity by jonathan.lee

I can confirm this is still happening in SQL Prompt 10.13.10.1356.  Any ETA on a fix or is there a workaround like directly editing a settings file? / comments
  1. Community
  2. SQL Prompt
  3. Tab Color Settings Not Saving Again
I can confirm this is still happening in SQL Prompt 10.13.10.1356.  Any ETA on a fix or is there a workaround like directly editing a settings file?
0 votes
SELECT in trigger (BP003) rule firing incorrectly
  1. Community
  2. SQL Prompt
SELECT in trigger (BP003) incorrectly fires for a SELECT statement in a trigger that is attached to a cursor.ALTER TRIGGER xxxx ON yyy.YYYYYY ....     DECLARE cur_updated CURSOR LOCAL FAST_FORWARD ...
2 followers 2 comments 0 votes
What I mean by closest match varies between match types. In the case for camel case (or underscore-separated first letter matching), the closest match would be the one that has the exact initials. Next closest would be ones with additional suffixes, those with prefixes, and then those with intervening content between matched initials. Somewhere in there should be any matches with the search value as a direct substring. For the case of substring matches, an exact match should be first, then matches closest to the beginning of the name should be listed next, sorted by suffix length (or alphabetical for the same match starting position). Matches further from the beginning of the string would then be listed, sorted as above, etc. Here are a few example based looking up a table name with the initials of "tcd" (while typing the FROM clause of a SELECT statement): Note: I've added square brackets around each matching, highlighted letter per the screenshot of the SQL Prompt suggestions. Closest match (the actual table I was searching for): [t]bl[C]oil_[D]ata Suffix to the match: [t]bl[C]oil_[D]ata_New Prefix to the match: Original_[t]bl[C]oil_[D]ata Match with intervening content: [t]bl[C]oil_Width_[D]ata. Mix of prefix and intervening content: Original_[t]bl[C]oil_Temperature_[D]ata Original_[t]bl[C]oil_Thickness_[D]ata Original_[t]blIMS_Exit_LP_[C]entreline_[D]ev Content as a direct substring: Temp[T][C][D] Another example, for a substring match, "stand" with no exact match (if one exists, it should be listed first, of course): tbl[Stand]s (shortest match) tbl[Stand]_Controllers tbl[Stand]_Controllers_AGC_Data tbl[Stand]_Controllers_CVC_Data <-- # 2 and 3 should be listed in alphabetical order (#1 would fall in the proper place that way too, so it might not need special handling) Original_tbl[Stand]_Controllers_AGC_Data <-- These next ones should be listed after 1-3 instead of before them, as happens currently. Original_tbl[Stand]_Controllers_HGC_Data Within each type of match, the content could be sorted alphabetically for matches with prefixes and suffixes and from shortest to longest for intervening content (could be number of words instead of total number of characters, one long word like "_temperature_" vs. two short words "_exit_lp_"). With the few (abbreviated) examples I gave, you might think this is much ado about nothing but when there are 20-40 match suggestions and the one you want is near the bottom of the list but should be been an exact match, it is a real pain. I hope this explanation is clearer. I will add this as a suggestion for new features. Thanks, Jonathan / comments
  1. Community
  2. SQL Prompt
  3. SQL Prompt suggestions order
What I mean by closest match varies between match types. In the case for camel case (or underscore-separated first letter matching), the closest match would be the one that has the exact initials....
0 votes
Total activity
5
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
2