SQLite column aliasing

Question

Premise I recently ran into a bug in a `select` statement in my code. It was fairly trivial to fix after I realized what was going on, but I'm interested in finding a way to make sure a similar bug doesn't happen again. Here's an example of an offending query: ``` select the, quick, brown fox, jumped, over, the, lazy, dog from table_name; ``` What I had intended was: ``` select the, quick, brown, fox, jumped, over, the, lazy, dog from table_name; ``` For those who don't see it, a comma is missing after `brown` in the former. This causes the column to be aliased, because the `as` keyword is not required. So, what you get in the result is: ``` the, quick, fox, jumped, over, the, lazy, dog ``` ...with all the values of `brown` in a column named `fox`. This can be noticed pretty easily for a short query like the above (especially when each column has very different values), but where it came up was in a fairly complicated query with mostly integer columns like this: ``` select foo, bar, b…

Accepted Answer

One thing that I've done before is to move the commas to the beginning of the line. This allows some benefits. First, you can instantly see if there are any commas missing. Second, you can add a new column at the end without having to modify the previously last line.

Missing:

```
select
  the
, quick
, brown
  fox
, jumped
, over
, the
, lazy
, dog
from table_name;
```

Not missing:

```
select
  the
, quick
, brown
, fox
, jumped
, over
, the
, lazy
, dog
from table_name;
```

SQLite column aliasing

Solution

Problem