MarkusWinand
Joined 12 years ago
Joined 12 years ago
Besides portability, there is IMHO nothing against INSERT ... ON CONFLICT if it does what you need.
It's there already!
It's in the chart as footnote "b": Outer reference must be the only argument (doesn’t support F441)
That's the one thing SQL Server doesn't eat. Those that are green in the chart work fine in this case.
I'd go for CHECK constraints first: https://www.sqlite.org/lang_createtable.html#ckconst
> Procedural SQL [...] Choose your investment here carefully.
I think that the demand for procedual code has dropped drastically in the past decades as the "normal" SQL can solve so many more things with window functions, recursion, and so forth. So I'd say: Yes, choose your investment wisely and stay away from procedural SQL as long as possible.
Can you tell me: what kind of identifier is it (view name, function name) and which SQL context it causes problems (select list, create/drop statement, ...) and which system has problems with it. Thx.
All charts on modern-sql.com are backed by tests. I also keep them up-to-date by running them for new releases when they appear.
All about SQL:
https://winand.at/ https://use-the-index-luke.com/ https://modern-sql.com/