Closed tkopets closed 7 years ago
Go head. Can you release the new version?
Sure, a bit later, as I want to fix few things before release.
Right now we have a problem when existing users most probably will not get the updated queries for different RDBMS as Sublime copies the entire contents of SQLTools.sublime-settings
into Users
directory file after plugin install, so the updated queries most probably will be overridden by queries defined in Users\SQLTools.sublime-settings
.
Any ideas on that topic?
I also want to write a short PackageContol update message
Yeah, we should start using update messages. I tried in the beginning but i give up right after.
On Wed, May 3, 2017 at 11:54 AM, Taras Kopets notifications@github.com wrote:
I also want to write a short PackageContol update message
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/mtxr/SQLTools/pull/85#issuecomment-298935409, or mute the thread https://github.com/notifications/unsubscribe-auth/AArL6UnHUi_8FtTGxF1diSQIZOFU9tSaks5r2JUTgaJpZM4NPL8o .
Do you have any ideas how to force Sublime not to copy entire SQLTools.sublime-settings
with contents, but to start with empty config in Users\SQLTools.sublime-settings
like this:
{
}
Or is there anything we can alter in SQLTools project structure to achieve this?
I think I found a way to do so.
New "smarter" completions are shown, when possible. The main difference from previous completions are proper completions for table columns:
table.column|
, as well as completions for table aliases:select a.| from tbl a
and completions for join conditions:select * from tbl_a a inner join tbl_b b on |
The current paragraph of SQL text is parsed by already existingsqlparse
library. A small demo can be seen in discussion https://github.com/mtxr/SQLTools/issues/67