3 ms·

While we are at it let's write SQL queries starting from FROM. `FROM users SELECT *` It'd allow tooling to provide IntelliSense better.

miohtama 5y ago
While this might be a joke, the world has been ripe for a replacement for SQL… for the last 20 years.
- hdjrudni 5y ago
  I started writing a new SQL parser that just transforms the query...this was one of the features. The other being a syntax for group-wise max queries which are just crazy dumb to write efficiently in MySQL.
- robocat 5y ago
  I could see some standardised SQL language extension, similar to how TypeScript extended JavaScript, that has a transformation phase into the native SQL dialect within the database access library, or via some middleware.
  - Too 5y ago
    LINQ?
vosper 5y ago
I agree, though I'll give SQL a pass for this because it's old. But how the Javascript world ever thought that `import { function } from 'library'` was better than `from 'library' import { function }` I'll never know. Python got this right long before anyone was even thinking about adding imports to JS!
- hdjrudni 5y ago
  Ya..that one is particularly sad because it was recent. Don't know why they felt the need to botch that.
- goscript 5y ago
  I agree but not with current JavaScript modules. i would rather work with this: import { functionA } from 'library'; import { functionB } from '../utils/core/abc'; import { functionC } from './a'; over: from 'library' import { functionA }; from '../utils/core/abc' import { functionB }; from './a' import { functionC };
  - Too 5y ago
    Care to rationalize? Your first example only looks pretty because the function names happens to be aligned while the library names are not. Import a few more functions with different length name and the story will be different. In reality library names tend to align better since they usually start with same prefix spanning across several sub-components.

miohtama 5y ago

While this might be a joke, the world has been ripe for a replacement for SQL… for the last 20 years.

hdjrudni 5y ago
I started writing a new SQL parser that just transforms the query...this was one of the features. The other being a syntax for group-wise max queries which are just crazy dumb to write efficiently in MySQL.
robocat 5y ago
I could see some standardised SQL language extension, similar to how TypeScript extended JavaScript, that has a transformation phase into the native SQL dialect within the database access library, or via some middleware.
- Too 5y ago
  LINQ?

vosper 5y ago

I agree, though I'll give SQL a pass for this because it's old. But how the Javascript world ever thought that `import { function } from 'library'` was better than `from 'library' import { function }` I'll never know. Python got this right long before anyone was even thinking about adding imports to JS!

hdjrudni 5y ago
Ya..that one is particularly sad because it was recent. Don't know why they felt the need to botch that.
goscript 5y ago
I agree but not with current JavaScript modules. i would rather work with this: import { functionA } from 'library'; import { functionB } from '../utils/core/abc'; import { functionC } from './a'; over: from 'library' import { functionA }; from '../utils/core/abc' import { functionB }; from './a' import { functionC };
- Too 5y ago
  Care to rationalize? Your first example only looks pretty because the function names happens to be aligned while the library names are not. Import a few more functions with different length name and the story will be different. In reality library names tend to align better since they usually start with same prefix spanning across several sub-components.