activerecord-nulldb-adapter 0.8.0 → 0.9.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4e4a403aa1ee43e02dd69b91820f308d5085e99eca0684879e60f7fe3d7872e1
-  data.tar.gz: 84abce618014d4bb49cb903eea65f15ae830de6216531d3e3af709d70d02c03c
+  metadata.gz: 0da8a5f679279b76c36a80995783db057cf0bbc680d4006209619d068c55fbf3
+  data.tar.gz: eb7c91fe3bd86f1d8787cd2dc394aeecc1b8c0950e7133fb4a21f74f6e596a8d
 SHA512:
-  metadata.gz: 1a6d28b99a18d0705990360b3775d040e78ab4842fc70a20216f8970615115f714112caef2d1b77d0758af32b1420a42d96c8785e1c0580af2523cec77533d32
-  data.tar.gz: 58b09c97d6777eac6fac477ce39d6297f19a7b8821d5e59af9661144aa673e8cfc5cff642798283bf0e8061e0532b231c802f7ef726ed1463b50deb576b04a82
+  metadata.gz: 87e4cb3496818735480c034bb2444bec7cdd60eb6032332d78875d3f1cd8bb769f256d70d8a80b254cc11d9c91564b76f32fe8f863d65dba5d13427a4d6f74d1
+  data.tar.gz: ae332ef581de6f46f46940d2f4c6a0011606abbe2432e258a88b7ab9b5c0be50af03a9b140b630c4e79228c3ed65d4569ae50f9e828ad37d3b64dc031de9bcbf

data/Appraisals

@@ -7,7 +7,7 @@ appraise "activerecord-6.0" do
 end
 
 appraise "activerecord-7.0" do
-  gem "activerecord", "~> 7.0.0.alpha2"
+  gem "activerecord", "~> 7.0.0"
 end
 
 appraise "activerecord-master" do

data/CHANGES.md

@@ -1,6 +1,14 @@
 Unreleased
 ----------
 
+0.9.0 (2023-03-10)
+-----------
+
+- Add support to BigSerial #119
+- Add support to hstore #118
+- Support Postgres type modifiers #117
+
+
 0.8.0 (2022-10-28)
 -----------
 

data/README.md

@@ -0,0 +1,157 @@
+[<img src="https://badge.fury.io/rb/activerecord-nulldb-adapter.png" alt="Gem
+Version" />](http://badge.fury.io/rb/activerecord-nulldb-adapter) [<img
+src="https://codeclimate.com/github/nulldb/nulldb.png"
+/>](https://codeclimate.com/github/nulldb/nulldb) [<img
+src="https://github.com/nulldb/nulldb/workflows/build/badge.svg?branch=master"
+alt="Build Status" />](https://github.com/nulldb/nulldb/actions)
+
+# The NullDB Connection Adapter Plugin
+
+## What
+
+NullDB is the Null Object pattern as applied to ActiveRecord database
+adapters.  It is a database backend that translates database interactions into
+no-ops.  Using NullDB enables you to test your model business logic -
+including `after_save` hooks - without ever touching a real database.
+
+## Compatibility
+
+### Ruby
+Currently supported Ruby versions: MRI 2.5.x, 2.6.x, 2.7.x, 3.X.
+
+Experimental support provided for: JRuby
+
+### ActiveRecord
+Any version of ActiveRecord >= 5.2
+
+It is tested against AR 5.2, 6.0, 6.1 and master branch.
+
+## Installation
+
+    gem install activerecord-nulldb-adapter
+
+## How
+
+Once installed, NullDB can be used much like any other ActiveRecord database
+adapter:
+
+    ActiveRecord::Base.establish_connection :adapter => :nulldb
+
+NullDB needs to know where you keep your schema file in order to reflect table
+metadata.  By default it looks in RAILS_ROOT/db/schema.rb.  You can override
+that by setting the `schema` option:
+
+    ActiveRecord::Base.establish_connection :adapter => :nulldb,
+                                            :schema  => 'foo/myschema.rb'
+
+NullDB comes with RSpec integration.  To replace the database with NullDB in
+all of your specs, put the following in your spec/rails_helper:
+
+    require 'nulldb_rspec'
+    include NullDB::RSpec::NullifiedDatabase
+
+after you load your rails environment
+
+    require File.expand_path('../config/environment', __dir__)
+
+otherwise you will encounter issues such as
+([bug)](https://github.com/nulldb/nulldb/pull/90#issuecomment-496690958).
+
+Or if you just want to use NullDB in a specific spec context, you can include
+the same module inside a context:
+
+    require 'nulldb_rspec'
+
+    describe Employee, "with access to the database" do
+      fixtures :employees
+      # ...
+    end
+
+    describe Employee, "with NullDB" do
+      include NullDB::RSpec::NullifiedDatabase
+      # ...
+    end
+
+If you want to have NullDB enabled by default but disabled for particular
+contexts then (see this
+[post)](https://web.archive.org/web/20120419204019/http://andywaite.com/2011/5
+/18/rspec-disable-nulldb)
+
+NullDB::Rspec provides some custom matcher support for verifying expectations
+about interactions with the database:
+
+    describe Employee do
+      include NullDB::RSpec::NullifiedDatabase
+
+      it "should cause an insert statement to be executed" do
+        Employee.create!
+        Employee.connection.should have_executed(:insert)
+      end
+    end
+
+UnitRecord-style verification that no database calls have been made at all can
+be achieved by using the special `:anything` symbol:
+
+    describe "stuff that shouldn't touch the database" do
+      after :each do
+        Employee.connection.should_not have_executed(:anything)
+      end
+      # ...
+    end
+
+You can also experiment with putting NullDB in your database.yml:
+
+    unit_test:
+      adapter: nulldb
+
+However, due to the way Rails hard-codes specific database adapters into its
+standard Rake tasks, you may find that this generates unexpected and
+difficult-to-debug behavior.  Workarounds for this are under development.
+
+## Why
+
+There are a number of advantages to writing unit tests that never touch the
+database.  The biggest is probably speed of execution - unit tests must be
+fast for test-driven development to be practical. Another is separation of
+concerns: unit tests should be exercising only the business logic contained in
+your models, not ActiveRecord. For more on why testing-sans-database is a good
+idea, see:
+http://www.dcmanges.com/blog/rails-unit-record-test-without-the-database.
+
+NullDB is one way to separate your unit tests from the database.  It was
+inspired by the [ARBS](http://arbs.rubyforge.org/) and
+[UnitRecord](http://unit-test-ar.rubyforge.org/) libraries.  It differs from
+them in that rather than modifying parts of ActiveRecord, it implements the
+same [semi-]well-documented public interface that the other standard database
+adapters, like MySQL and SQLServer, implement. This has enabled it to evolve
+to support new ActiveRecord versions relatively easily.
+
+One concrete advantage of this null-object pattern design is that it is
+possible with NullDB to test `after_save` hooks.  With NullDB, you can call
+`#save` and all of the usual callbacks will be called - but nothing will be
+saved.
+
+## Limitations
+
+*   It is **not** an in-memory database.  Finds will not work.  Neither will
+    `reload`, currently.  Test fixtures won't work either, for obvious
+    reasons.
+*   It has only the most rudimentery schema/migration support.  Complex
+    migrations will probably break it.
+*   Lots of other things probably don't work.  Patches welcome!
+
+
+## Who
+
+NullDB was originally written by Avdi Grimm <mailto:avdi@avdi.org>. It is
+currently maintained by [Danilo Cabello](https://github.com/cabello).
+Previously maintained by: [Bram de Vries](https://github.com/blaet).
+
+## Where
+
+*   Homepage: https://github.com/nulldb/nulldb
+
+
+## License
+
+See the LICENSE file for licensing information.

data/Rakefile

@@ -9,6 +9,6 @@ task :default => :spec
 
 require 'rdoc/task'
 Rake::RDocTask.new do |rd|
-  rd.main = "README.rdoc"
-  rd.rdoc_files.include("README.rdoc", "LICENSE", "lib/**/*.rb")
+  rd.main = "README.md"
+  rd.rdoc_files.include("README.md", "LICENSE", "lib/**/*.rb")
 end

data/activerecord-nulldb-adapter.gemspec

@@ -14,7 +14,7 @@ Gem::Specification.new do |s|
   s.email = "cabello@users.noreply.github.com"
   s.extra_rdoc_files = [
     "LICENSE",
-    "README.rdoc"
+    "README.md"
   ]
   s.files    = `git ls-files`.split($/)
   s.homepage = "https://github.com/nulldb/nulldb"

data/gemfiles/activerecord_7.0.gemfile

@@ -2,7 +2,7 @@
 
 source "https://rubygems.org"
 
-gem "activerecord", "~> 7.0.0.alpha2"
+gem "activerecord", "~> 7.0.0"
 
 group :development, :test do
   gem "spec"

data/lib/active_record/connection_adapters/nulldb_adapter/core.rb

@@ -343,13 +343,37 @@ class ActiveRecord::ConnectionAdapters::NullDBAdapter < ActiveRecord::Connection
     [nil, @logger, @config]
   end
 
+  # Register types only once to avoid ActiveRecord::TypeConflictError
+  # in ActiveRecord::Type::Registration#<=>
+  REGISTRATION_MUTEX = Mutex.new
+
   def register_types
-    require 'active_model/type'
+    REGISTRATION_MUTEX.synchronize do
+      return if self.class.types_registered
+
+      self.class.types_registered = true
+    end
+
     ActiveRecord::Type.register(
       :primary_key,
       ActiveModel::Type::Integer,
       adapter: adapter_name,
       override: true
     )
+
+    ActiveRecord::Type.add_modifier({ array: true }, DummyOID, adapter: :nulldb)
+    ActiveRecord::Type.add_modifier({ range: true }, DummyOID, adapter: :nulldb)
+  end
+
+  class << self
+    attr_accessor :types_registered
+  end
+
+  class DummyOID < ActiveModel::Type::Value
+    attr_reader :subtype
+
+    def initialize(*args)
+      @subtype = args.first
+    end
   end
 end

data/lib/active_record/connection_adapters/nulldb_adapter/table_definition.rb

@@ -7,7 +7,9 @@ class ActiveRecord::ConnectionAdapters::NullDBAdapter
     alias_method :interval, :text
     alias_method :geometry, :text
     alias_method :serial, :integer
+    alias_method :bigserial, :integer
     alias_method :inet, :string
     alias_method :jsonb, :json if method_defined? :json
+    alias_method :hstore, :json
   end
 end

data/lib/nulldb/version.rb

@@ -1,3 +1,3 @@
 module NullDB
-  VERSION = "0.8.0"
+  VERSION = "0.9.0"
 end

data/spec/nulldb_spec.rb

@@ -490,6 +490,7 @@ describe 'adapter-specific extensions' do
           t.interval :time_interval
           t.geometry :feature_geometry, srid: 4326, type: "multi_polygon"
           t.jsonb :jsonb_column
+          t.hstore :hstore_column
         end
       end
     }.to_not raise_error
@@ -503,6 +504,20 @@ describe 'adapter-specific extensions' do
     should_have_column(ExtendedModel, :jsonb_column, :json)
   end
 
+  it 'supports ActiveModel attributes with postgres modifiers' do
+    class ExtendedModel < ActiveRecord::Base
+      attribute :strings, :string, array: true
+      attribute :size, :integer, range: true
+    end
+
+    expect(ExtendedModel.type_for_attribute(:strings))
+      .to be_a ActiveRecord::ConnectionAdapters::NullDBAdapter::DummyOID
+    expect(ExtendedModel.new(strings: %w[a b]).strings).to eq %w[a b]
+    expect(ExtendedModel.type_for_attribute(:size))
+      .to be_a ActiveRecord::ConnectionAdapters::NullDBAdapter::DummyOID
+    expect(ExtendedModel.new(size: 1..5).size).to eq 1..5
+  end
+
   it 'registers a primary_key type' do
     expect(ActiveRecord::Type.lookup(:primary_key, adapter: 'NullDB'))
       .to be_a(ActiveModel::Type::Integer)

metadata

@@ -1,16 +1,16 @@
 --- !ruby/object:Gem::Specification
 name: activerecord-nulldb-adapter
 version: !ruby/object:Gem::Version
-  version: 0.8.0
+  version: 0.9.0
 platform: ruby
 authors:
 - Avdi Grimm
 - Myron Marston
 - Danilo Cabello
-autorequire: 
+autorequire:
 bindir: bin
 cert_chain: []
-date: 2021-10-29 00:00:00.000000000 Z
+date: 2023-03-10 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activerecord
@@ -138,7 +138,7 @@ executables: []
 extensions: []
 extra_rdoc_files:
 - LICENSE
-- README.rdoc
+- README.md
 files:
 - ".github/workflows/ruby.yml"
 - ".gitignore"
@@ -146,7 +146,7 @@ files:
 - CHANGES.md
 - Gemfile
 - LICENSE
-- README.rdoc
+- README.md
 - Rakefile
 - activerecord-nulldb-adapter.gemspec
 - gemfiles/activerecord_5.2.gemfile
@@ -180,7 +180,7 @@ homepage: https://github.com/nulldb/nulldb
 licenses:
 - MIT
 metadata: {}
-post_install_message: 
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -195,8 +195,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.1.4
-signing_key: 
+rubygems_version: 3.3.26
+signing_key:
 specification_version: 4
 summary: The Null Object pattern as applied to ActiveRecord database adapters
 test_files: []

data/README.rdoc

@@ -1,154 +0,0 @@
-{<img src="https://badge.fury.io/rb/activerecord-nulldb-adapter.png" alt="Gem Version" />}[http://badge.fury.io/rb/activerecord-nulldb-adapter]
-{<img src="https://codeclimate.com/github/nulldb/nulldb.png" />}[https://codeclimate.com/github/nulldb/nulldb]
-{<img src="https://github.com/nulldb/nulldb/workflows/build/badge.svg?branch=master" alt="Build Status" />}[https://github.com/nulldb/nulldb/actions]
-
-
-= The NullDB Connection Adapter Plugin
-
-== What
-
-NullDB is the Null Object pattern as applied to ActiveRecord database
-adapters.  It is a database backend that translates database
-interactions into no-ops.  Using NullDB enables you to test your model
-business logic - including +after_save+ hooks - without ever touching
-a real database.
-
-== Compatibility
-
-=== Ruby
-Currently supported Ruby versions: MRI 2.5.x, 2.6.x, 2.7.x, 3.X.
-
-Experimental support provided for: JRuby
-
-=== ActiveRecord
-Any version of ActiveRecord >= 5.2
-
-It is tested against AR 5.2, 6.0, 6.1 and master branch.
-
-== Installation
-
-  gem install activerecord-nulldb-adapter
-
-== How
-
-Once installed, NullDB can be used much like any other ActiveRecord
-database adapter:
-
-  ActiveRecord::Base.establish_connection :adapter => :nulldb
-
-NullDB needs to know where you keep your schema file in order to
-reflect table metadata.  By default it looks in
-RAILS_ROOT/db/schema.rb.  You can override that by setting the
-+schema+ option:
-
-  ActiveRecord::Base.establish_connection :adapter => :nulldb,
-                                          :schema  => 'foo/myschema.rb'
-
-NullDB comes with RSpec integration.  To replace the database with
-NullDB in all of your specs, put the following in your
-spec/rails_helper:
-
-  require 'nulldb_rspec'
-  include NullDB::RSpec::NullifiedDatabase
-
-after you load your rails environment
-
-  require File.expand_path('../config/environment', __dir__)
-
-otherwise you will encounter issues such as (bug)[https://github.com/nulldb/nulldb/pull/90#issuecomment-496690958].
-
-Or if you just want to use NullDB in a specific spec context, you can
-include the same module inside a context:
-
-  require 'nulldb_rspec'
-
-  describe Employee, "with access to the database" do
-    fixtures :employees
-    # ...
-  end
-
-  describe Employee, "with NullDB" do
-    include NullDB::RSpec::NullifiedDatabase
-    # ...
-  end
-
-If you want to have NullDB enabled by default but disabled for particular contexts then (see this post)[https://web.archive.org/web/20120419204019/http://andywaite.com/2011/5/18/rspec-disable-nulldb]
-
-NullDB::Rspec provides some custom matcher support for verifying
-expectations about interactions with the database:
-
-  describe Employee do
-    include NullDB::RSpec::NullifiedDatabase
-
-    it "should cause an insert statement to be executed" do
-      Employee.create!
-      Employee.connection.should have_executed(:insert)
-    end
-  end
-
-UnitRecord-style verification that no database calls have been made at
-all can be achieved by using the special +:anything+ symbol:
-
-  describe "stuff that shouldn't touch the database" do
-    after :each do
-      Employee.connection.should_not have_executed(:anything)
-    end
-    # ...
-  end
-
-You can also experiment with putting NullDB in your database.yml:
-
-  unit_test:
-    adapter: nulldb
-
-However, due to the way Rails hard-codes specific database adapters
-into its standard Rake tasks, you may find that this generates
-unexpected and difficult-to-debug behavior.  Workarounds for this are
-under development.
-
-== Why
-
-There are a number of advantages to writing unit tests that never
-touch the database.  The biggest is probably speed of execution - unit
-tests must be fast for test-driven development to be practical.
-Another is separation of concerns: unit tests should be exercising
-only the business logic contained in your models, not ActiveRecord.
-For more on why testing-sans-database is a good idea, see:
-http://www.dcmanges.com/blog/rails-unit-record-test-without-the-database.
-
-NullDB is one way to separate your unit tests from the database.  It
-was inspired by the ARBS[http://arbs.rubyforge.org/] and
-UnitRecord[http://unit-test-ar.rubyforge.org/] libraries.  It differs
-from them in that rather than modifying parts of ActiveRecord, it
-implements the same [semi-]well-documented public interface that the
-other standard database adapters, like MySQL and SQLServer,
-implement. This has enabled it to evolve to support new ActiveRecord
-versions relatively easily.
-
-One concrete advantage of this null-object pattern design is that it
-is possible with NullDB to test +after_save+ hooks.  With NullDB, you
-can call +#save+ and all of the usual callbacks will be called - but
-nothing will be saved.
-
-== Limitations
-
-* It is *not* an in-memory database.  Finds will not work.  Neither
-  will +reload+, currently.  Test fixtures won't work either, for
-  obvious reasons.
-* It has only the most rudimentery schema/migration support.  Complex
-  migrations will probably break it.
-* Lots of other things probably don't work.  Patches welcome!
-
-== Who
-
-NullDB was originally written by Avdi Grimm <mailto:avdi@avdi.org>.
-It is currently maintained by {Danilo Cabello}[https://github.com/cabello].
-Previously maintained by: {Bram de Vries}[https://github.com/blaet].
-
-== Where
-
-* Homepage: https://github.com/nulldb/nulldb
-
-== License
-
-See the LICENSE file for licensing information.