PoorSQL

Free open-source T-SQL formatter with SSMS, VS, and Notepad++ plugins, command-line/bulk formatter, and .Net and JS libraries. Easy SQL formatting, anywhere!

[James Ide @JI]

With the newest version of Git 2.37.0, you can run just "git push" to push new branches. No more "--set-upstream origin". Enable with:

git config --global --add --bool push.autoSetupRemote true

[PoorSQL @PoorSQL]

Hopefully last in the recent round of VS and SSMS extension updates now available: https://t.co/FvMTYJJlsQ and https://t.co/9ZtBQR0akm. VS2015 is again supported in the standard/current version, and SSMS compatibility issues hopefully addressed.

[PoorSQL @PoorSQL]

@mkristensen @spottedmahn Aaand, once again, never mind, Shell.Immutable.14.0 was actually resolving to v15.0.0.0 and I somehow missed it, even while I was typing the message above. All set again with the 14.0.0.0 reference.

[PoorSQL @PoorSQL]

@mkristensen @spottedmahn Thought it was working, but stuck. With Shell.14.0 (v14), Shell.Immutable.10.0 (v10), and Shell.Immutable.14.0 (v14), can't find symbol ServiceProgressData, and VS only offers Shell.Framework (v15) to fix it. Docs say Shell.Immutable.14.0 should have it... https://t.co/kMtuswFyUZ

[PoorSQL @PoorSQL]

@mkristensen @spottedmahn Hmm, using https://t.co/NvV925ru78.14.0 the async/await / base.InitializeAsync stuff seemed to get a whole lot more complicated, so I used https://t.co/NvV925ru78.15.0 instead... Any advice as to how to do https://t.co/HGAgCCsNnf cleanly with https://t.co/NvV925ru78.14.0?

[PoorSQL @PoorSQL]

One release, and two fatal issues so far for SSMS. Manual release pipelines suck, especially when only exercised once every couple of years. SSMS Package Installer fixed, available for download as 1.6.13b. My apologies (again!) to the 200 or so ppl with bad downloads.

[PoorSQL @PoorSQL]

@jwk6 Sorry about that, fixed, and thanks for the fast feedback!

[PoorSQL @PoorSQL]

Finally released SSMS 18 and VS 2019 support for Poor Man's T-SQL Formatter. Sorry about the wait: https://t.co/K0wYDDlo5H / https://t.co/00RMmLGVqd

[PoorSQL @PoorSQL]

If you're stuck in https://t.co/4A9z6L0Yrr v1.6.10 with chrome bug https://t.co/gQhu1eL4ws, There's a workaround: Settings -> Advanced Settings (bottom of page) -> Content Settings -> Cookies -> See All Cookies and Site Data -> search "poorsql" -> hit the trash icon. You're free!

[PoorSQL @PoorSQL]

https://t.co/4A9z6L0Yrr update: now available on HTTPS, eg https://t.co/KLMwXdXAek! This also happens to be a workaround for the Chrome bug that gets you stuck on v1.6.10 of the site forever... Current version is v1.6.10b.

[PoorSQL @PoorSQL]

"Fun" Chrome bug: If you were using AppCache on an insecure origin, users your site can be stuck the version of the site they had at time of Chrome Upgrade - unrecoverable, by the looks of it! Workarounds wanted! https://t.co/RBE3BMMv9K. This impacts https://t.co/REUSM077Rs

[PoorSQL @PoorSQL]

https://t.co/4A9z6L0Yrr bug: As AppCache is no longer supported for insecure origins in recent versions of Chrome, offline mode does not work anymore. https://t.co/lMMQGyaN3g

[PoorSQL @PoorSQL]

@databoffin Good question! Yes, in the sense that I'm hosting, checking twitter, and occasionally answering email. Yes, in the sense that I occasionally make changes to support ongoing availability eg in NPP7.6.4 and VSCode. No, in the sense that I've made no attempt to add features in years

[PoorSQL @PoorSQL]

@jonjaaay Hi @jonjaaay, you shouldn't need to download the package manually anymore since Notepad++ 7.6.4 (released today), the formatter is finally included in the Plugin Admin list. That said, the error you got is not uncommon in windows 10, you really do need to install .Net 3.5(/2).

[PoorSQL @PoorSQL]

@jahnavi_patel2 Hi, I don't have a Mac handy to test, but should be just like any other extensions. In Windows that's File -> Preferences -> Settings -> Extensions -> Poor Man's SQL Formatting. For keyboard mappings, File -> Preferences -> Keyboard Shortcuts and type "Format" in the filter.

[PoorSQL @PoorSQL]

Atom plugin finally fixed after more than a year broken. Obviously I'm embarassed, but a also a little confused and relieved about how few people noticed...

[PoorSQL @PoorSQL]

@dirt_kael Sorry, the parser's all confused... I'm surprised you don't get an error highlight in fact. I would argue that a more "standard" and legible way to write this SQL would be to move the "ON B.key2 = A.KEY" bit to just after "INNER JOIN B". Existing Issue: https://t.co/rJwtpmqlVq

[PoorSQL @PoorSQL]

@taufikshaikh @KC_College Oops, clearly I misunderstood, that was not an individual's twitter handle. Anyway, also reported by email. :)

[PoorSQL @PoorSQL]

@taufikshaikh @KC_College also just reported the same issue by email, two days ago. I had never noticed it before, but I now see that an issue had been opened back in January, that I never saw: https://t.co/UajQvjZTyc . Don't know what the problem is, but sounds like it needs some attention.