3 ms·
I do this as well. on top i often do a pad entry so that the elements are all on their own line SELECT 1 as pad , a , b then i can reorder lines tr
by tezza 2y ago
I do this as well.
on top i often do a pad entry so that the elements are all on their own line
SELECT 1 as pad
, a
, b
then i can reorder lines trivially without stopping to re-comma the endpoints or maintain which special entry is on the line of the SELECT token
what would be helpful is both LEADING and trailing commas
so I am suggesting:
SELECT
, a
, b
would be permissible too. The parsing step is no longer the difficult portion.
Developer ease leads to less mistakes is my conjecture.
- mewpmewp2 2y agoWhy not something like SELECT a, b, c, 1 as pad FROM Then?
- tezza 2y agocool, that would work too. my preference is leading separators so the separators are all in a visual column. being in a visual column allows the eye to discount the separators easily. typically names are different lengths and the commas are hard/harder to spot Your suggestion: SELECT first_column, second_column_wider_a_lot, (third + fourth_combined_expression), 1 as pad FROM vs my current preference: SELECT 1 as pad , first_column , second_column_wider_a_lot , (third + fourth_combined_expression) FROM