arel_extensions 2.0.21 → 2.2.2

data/CONTRIBUTING.md

@@ -0,0 +1,102 @@
+# Contributing
+
+Your PRs are welcome.
+
+## Local Development
+
+Let's say you want to develop/test for `ruby 2.7.5` and `rails 5.2`.
+
+You will need to fix your ruby version:
+
+```bash
+rbenv install 2.7.5
+rbenv local 2.7.5
+```
+
+Fix your gemfiles:
+
+```bash
+bundle config set --local gemfile ./gemfiles/rails6.gemfile
+cp gemspecs/arel_extensions-v2.gemspec arel_extensions.gemspec
+```
+
+Or by copying:
+
+```bash
+cp gemfiles/gemfiles/rails6.gemfile Gemfiles
+cp gemspecs/arel_extensions-v2.gemspec arel_extensions.gemspec
+```
+
+Install dependencies:
+```bash
+bundle install
+```
+
+> [!IMPORTANT]
+> Sometimes you might need to delete `vendor` dirs.
+> If you use `bundle config set --local gemfile`, it will be in `gemfiles/vendor`.
+> If you just `cp gemfiles/…`, it will be in `vendor`.
+
+Develop, then test:
+
+```bash
+bundle exec rake test:to_sql
+```
+
+Refer to the [Version Compatibility](#version-compatibility) section to correctly
+set your gemfile.
+
+## Testing many DBs without installing them
+
+We provide a `docker compose` to set up some databases for testing:
+
+```bash
+docker compose -f dev/compose.yaml up --exit-code-from arelx
+```
+
+Or simply call `bin/compose`.
+
+The databases, versions of arelx, and versions of ruby are all read from the
+matrixes defined in `.github/workflow/ruby.yml`. To test a specific
+configuration, all you have to do is comment the versions you're not
+insterested in.
+
+> [!IMPORTANT]
+> This methods conflicts with the [Local development](#local-development) method.
+> If you find yourself jumping between both, make sure you delete `Gemfile.lock`
+> and `vendor/`.
+
+### VSCode
+
+You can use the following `launch.json` to debug:
+
+```json
+{
+  "version": "0.2.0",
+  "configurations": [
+    {
+      "type": "rdbg",
+      "name": "Debug DB",
+      "request": "launch",
+      "cwd": "${workspaceRoot}",
+      "script": "test/with_ar/all_agnostic_test.rb",
+      "command": "bundle exec ruby -Ilib -Itest",
+      "env": {
+        "DB": "postgresql"
+      },
+      "useBundler": false,
+      "askParameters": false
+    },
+    {
+      "type": "rdbg",
+      "name": "Debug to_sql",
+      "request": "launch",
+      "cwd": "${workspaceRoot}",
+      "script": "test/visitors/test_to_sql.rb",
+      "command": "bundle exec ruby -Ilib -Itest",
+      "useBundler": false,
+      "askParameters": false
+    }
+  ]
+}
+```

data/Gemfile

@@ -1,24 +1,3 @@
-source "https://rubygems.org"
+source 'https://rubygems.org'
 
-gemspec
-
-group :development, :test do
-  gem "sqlite3", '<= 1.3.13', platforms: [:mri, :mswin, :x64_mingw, :mingw]
-  gem "mysql2", '0.4.10', platforms: [:mri, :mswin, :x64_mingw, :mingw]
-  gem "pg", '< 1', platforms: [:mri, :mingw, :x64_mingw, :mswin]
-
-  gem "jdbc-sqlite3", platforms: :jruby
-  gem "activerecord-jdbcsqlite3-adapter", platforms: :jruby
-  gem "activerecord-jdbcmysql-adapter", platforms: :jruby
-  gem "activerecord-jdbcpostgresql-adapter", platforms: :jruby
-
-  gem "tiny_tds", '~> 1.3.0',require: false, platforms: [:mri,:mingw, :x64_mingw, :mswin]
-  gem "activerecord-sqlserver-adapter", '~> 4.2.0', platforms: [:mri, :mingw, :x64_mingw, :mswin]
-
-  gem 'ruby-oci8', platforms: [:mri, :mswin, :x64_mingw, :mingw]
-  gem 'activerecord-oracle_enhanced-adapter', '~> 1.6.0'
-
-  gem 'activesupport', '~> 4.0'
-  gem 'activemodel', '~> 4.0'
-  gem 'activerecord', '~> 4.0'
-end
+gemspec path: Dir.pwd

data/NEWS.md

@@ -0,0 +1,89 @@
+# News
+
+## [unreleased]
+
+## Release v2.2.2/v1.4.2 (27-11-2024)
+
+- Fix deprecartion warnings for `==` and `!=`, showing the true location.
+- Always emit deprecartion warnings for `==` and `!=`.
+
+## Release v2.2.1/v1.4.1 (08-11-2024)
+
+- Improved deprecartion warnings for `==` and `!=`, showing the location where they're called.
+
+## Release v2.2.0/v1.4.0
+
+- MS SQL: restrict date-quoting to Arel <= 6 (Rails 4.2)
+- MS SQL: turn on warnings on requires only when gem is found
+- Rails: 7.2 support for mysql, postgres, and sqlite.
+- Attributes: deprecate `==` and `!=`. They're causing issues with
+  `active_record`, and they're not sanitary.
+
+## Release v2.1.11/v1.3.11
+
+- MS SQL: turn on warnings on requires only when necessary.
+
+## Release v2.1.10/v1.3.10
+
+- MS SQL: add support for jruby 9.4 via [activerecord-jdbc-alt-adapter](https://rubygems.org/gems/activerecord-jdbc-alt-adapter/)
+
+## Release v2.1.9/v1.3.9
+
+### Bug Fixes
+
+- Postgres:
+  - Datetime formatting in postgres now behaves like mysql: if the target
+    timezone is a string, we automatically consider that you're trying to
+    convert from `UTC`.
+  - Datetime casting will now automatically ask for a
+    `timestamp without timezone`, also aligning with the expected befavior
+    in mysql. This also makes casting work better with timezone conversion,
+    especially if you don't pass the timezone from which you're converting
+    to.
+    ```ruby
+    scope
+      .select(Arel.quoted('2022-02-01 10:42:00')
+      .cast(:datetime)
+      .format_date('%Y/%m/%d %H:%M:%S', 'Europe/Paris')
+      .as('res'))
+    ```
+    Will produce:
+    ```sql
+    SELECT TO_CHAR(
+        CAST('2022-02-01 10:42:00' AS timestamp without time zone) AT TIME ZONE 'UTC' AT TIME ZONE 'Europe/Paris',
+        'YYYY/MM/DD HH24:MI:SS'
+      )
+      AS "res"
+    -- …
+    ```
+
+## Release v2.1.7/v1.3.7
+
+### New Features
+
+- `o.format_date` as an alternative to `o.format`
+  The actual behavior of `format` is inconsistent across DB vendors: in mysql we
+  can format dates and numbers with it, and in the other ones we only format
+  dates.
+
+  We're planning on normalizing this behavior. We want `format` to "cleverly"
+  format dates or numbers, and `format_date` / `format_number` to strictly
+  format dates / numbers.
+
+  The introduction of `format_date` is the first step in this direction.
+
+## Release v2.1.6/v1.3.6
+
+### Bug Fixes
+
+- This used to fail.
+  ```
+  Arel.when(a).then(b).format('%Y-%m-%d')
+  ```
+
+### New Features
+
+- `o.present`, a synonym for `o.not_blank`
+- `o.coalesce_blank(a, b, c)`
+- `o.if_present`, if the value is `null` or blank, then it returns `null`,
+  otherwise, it returns the value.  Inspired by rails' `presence`.