Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

SQL style guide by Simon Holywell

sqlstyle.guide

Post reply on HN
Print view View original

71–76 of 76 posts

Re: SQL style guide by Simon Holywell

#71

Post by asdfasvea »

jkubicek wrote: post #3

I've stopped using aliases in the SQL I write and it's dramatically increased the clarify. From this style guide, the aliases section would look like this in my style guide: SELECT first_name FROM staff JOIN students ON students.mentor_id = staff.staff_num;

Agree. In my experience people use aliases to use aliases. They know them but don't understand them.

Aliases are the SQL equivalent of ternary operators. Are you trying to write clean code or are you trying to express to other people you know things?

Re: SQL style guide by Simon Holywell

#73

Post by mustime »

ivanb wrote: post #35

SQL is around 40 and there is still no reliable tool for SQL formatting comparable to Prettier or gofmt. At least not for Postgres. There are several formatters but they break on advanced features like stored procedures. If someone is looking for an open source project to contribute to, a tool like this would be greatly appreciated.

[dead]

Re: SQL style guide by Simon Holywell

#74

Post by emmelaich »

mijamo wrote: post #58
wcrossbow wrote: post #52

Earlier quoted context omitted.

Editors can highlight SQL queries embedded as strings. Neovim can do it, and I'm pretty confident it's not going to be alone in that respect. edit: Not the editor I use but thought it might be helpful. Here is an extension, which I haven't tested, to do this in VSCode: https://marketplace.visualstudio.com/items?itemName=iuyoy.hi...

I have never seen a syntax highlighter for SQL that actually covers the real deal from Postgres dialect. Basic stuff is covered and then suddenly you use a combination that isn't covered and the colors are all wrong. This is even true for pgadmin, which is ironic. Unlike most programming languages, SQL built in syntax is huuuuuge and it is very hard to cover it all, especially as it varies with the dialect.

Maybe it's time for programming languages for use something like markdown in strings for embedded sql and dsl. e.g.

```sql

```

Re: SQL style guide by Simon Holywell

#75

Post by jd3 »

tankenmate wrote: post #56
jd3 wrote: post #44

Earlier quoted context omitted.

A week before being laid off last month, I solved a decade+ old open problem at our company which first occurred since Django doesn't natively support CTE's, leading to years of technical debt from the ersatz sql/query plans produced by our fragile queries. I ended up manually overloading get_extra_restriction on a custom ForeignKey class (we couldn't use FilteredRelation b/c we were still on django 1.11), which ensu…

Good call. As an aside why not use postgres's mysql foreign data wrapper instead of syncing with the mysql database?

I was not tech lead on that part of the project and did not contribute to any of its initial research/implementation, sadly; I was brought in post-hoc to help with perf issues/cleanup.

To directly answer your question, though, without going into too much detail, there were pci compliance issues with some tables/columns in the mysql db, so if I had to guess, perhaps DMS had the capability to assuage that concern more elegantly than mysql_fdw[0], though the mysql_fwd EXCEPT parameter seems to also do the same thing, so honestly, I have no idea.

    By default, all views and tables existing in a particular database on the MySQL host are imported. Using this option, you can exclude specified foreign tables from the import.[1]
[0]: https://github.com/EnterpriseDB/mysql_fdw

[1]: https://www.enterprisedb.com/docs/mysql_data_adapter/latest/...

Re: SQL style guide by Simon Holywell

#76

Post by dagss »

mijamo wrote: post #58
wcrossbow wrote: post #52

Earlier quoted context omitted.

Editors can highlight SQL queries embedded as strings. Neovim can do it, and I'm pretty confident it's not going to be alone in that respect. edit: Not the editor I use but thought it might be helpful. Here is an extension, which I haven't tested, to do this in VSCode: https://marketplace.visualstudio.com/items?itemName=iuyoy.hi...

I have never seen a syntax highlighter for SQL that actually covers the real deal from Postgres dialect. Basic stuff is covered and then suddenly you use a combination that isn't covered and the colors are all wrong. This is even true for pgadmin, which is ironic. Unlike most programming languages, SQL built in syntax is huuuuuge and it is very hard to cover it all, especially as it varies with the dialect.

I use Jetbrains and there is at least full coverage for MSSQL in my experience, which is a huge dialect -- not only syntax highlighting but full IDE features like autocompletion and target name refactoring etc.

And 10 other dialects are listed..

Post reply on HN