| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Arel: Implemented DB-aware NULL-safe comparison (#34451) | Dmytro Shteflyuk | 2018-11-15 | 1 | -0/+2 |
| | | | | | | | | | | * Arel: Implemented DB-aware NULL-safe comparison * Fixed where clause inversion for NULL-safe comparison * Renaming "null_safe_eq" to "is_not_distinct_from", "null_safe_not_eq" to "is_distinct_from" [Dmytro Shteflyuk + Rafael Mendonça França] | ||||
| * | Remove `visit_Fixnum` and `visit_Bignum` | Ryuta Kamizono | 2018-09-30 | 1 | -2/+0 |
| | | | | | Follow up ae406cd633dab2cafbc0d1bb5922d1ca40056ea0. | ||||
| * | Abandon TOP support. | Vladimir Kochnev | 2018-09-25 | 1 | -1/+0 |
| | | | | | | | | | | | | | | | | | Initially, `TOP` was introduced to support `limit` for MSSQL database. Unlike PostgreSQL/MySQL/SQLite, MSSQL does not have native `LIMIT`/`OFFSET` support. The commit adding `TOP` is 1a246f71616cf246a75ef6cbdb56032e43d4e643. However, it figured out that `TOP` implementation was weak and it's not sufficient to also support `OFFSET`, then `TOP` was substituted with `ROW_NUMBER()` subquery in be48ed3071fd6524d0145c4ad3faeb4aafe3eda3. This is a well known trick in MSSQL - https://stackoverflow.com/questions/2135418/equivalent-of-limit-and-offset-for-sql-server. So now we don't need this `visit_Arel_Nodes_Top` at all. It does nothing useful but also adds an extra space after `SELECT` when `LIMIT` is being used for **any** database. | ||||
| * | Arel: :nodoc: all | Matthew Draper | 2018-02-24 | 1 | -1/+1 |
| | | |||||
| * | Arel: rubocop -a | Matthew Draper | 2018-02-24 | 1 | -186/+187 |
| | | |||||
| * | Merge Arel into Active Record | Matthew Draper | 2018-02-24 | 1 | -0/+199 |
 |
index : rails.git | |
| Mirror of official rails repo with custom fixes. | Harald Eilertsen |
| aboutsummaryrefslogtreecommitdiffstats |