AnyhowStep

SQLite truncates. MySQL and PostgreSQL round.

```sql SELECT unix_timestamp('2038-01-20'); > 0 ``` The `bugs.mysql.com` link has workarounds for some of the Y2038-related problems. However, there are probably other problems that need to be investigated.

https://bugs.mysql.com/bug.php?id=71758

https://dev.mysql.com/worklog/task/?id=1872#targetText=Currently%20we%20support%20only%20dates,internal%20representation%20of%20TIMESTAMP%20type.

We are abusing an aggregate function, derived table, and compound query just to get integer overflow errors...

I don't know what madness inspired me to come up with this workaround. I regret it now because I'm seriously considering this... user-defined functions are more "elegant" but it means...

We want a throw-on-overflow addition operator, and not a cast-on-overflow operator, because of this, ```sql SELECT (9223372036854775807+9223372036854775807)/9973 ``` This should throw. But on SQLite, we get `1849668512354311.8` It is decidedly...

GraphQL and SQL are very different things. In particular, GraphQL doesn't support the kind of arbitrary expressions and nested expressions that SQL does. There **are** GraphQL libraries for SQL databases,...

Relevant links, + http://mailinglists.sqlite.org/cgi-bin/mailman/private/sqlite-users/2020-March/088723.html + https://www.sqlite.org/src/tktview?name=3c9eadd2a6 + https://www.sqlite.org/src/timeline?r=do-not-factor-functions > > > While ORACLE does state that COALESCE will short circuit, > > A similar problem was reported on a ticket...

When using grouping sets, columns not in the pairwise intersection of the grouping sets are nullable. For example, given `GROUPING SETS ((id, a), (id, b))`, `a` and `b` are nullable.