Warning on missing alias

[JasonShin]

Feature:

You would get this if you have a query that's like

const sql3 = sql`
SELECT items.id
FROM items
`

TODO

• Update docs

[nicoabie]

I believe people will hate the tool if you throw warnings where there are no conflicts.

It would be healthier to error out if two columns clash like

select a.someName, b.someName .... that is definitely an error

[JasonShin]

@nicoabie 🤷‍♂️ that's kind of already happening from the DB level already
If you

SELECT tableA.id, tableB.id
FROM tableA
JOIN tableB ON tableA.id = tableB.tableA_id

You would get clashing column names id, id.

I'm still leaning towards throwing warning and then in V1, make it throw an error but have a configuration to warn only if the user wants.

But you have a good point. I will handle the clashing name problem next

[nicoabie]

Correct, that sql should rise an error whereas the example you posted that raises a warning should be ok.

Do you see the difference?
People will get annoyed if you always rise warnings and will omit them. Then they will have columns clashing

The only way of really help them is rising an error when columns clash