rails--rails/activestorage/test/database/setup.rb

# frozen_string_literal: true

require_relative "create_users_migration"

ActiveRecord::Base.establish_connection(adapter: "sqlite3", database: ":memory:")
ActiveRecord::Base.connection.migration_context.migrate
ActiveStorageCreateUsers.migrate(:up)
Use frozen string literal in Active Storage 2017-08-12 08:32:15 -04:00			`# frozen_string_literal: true`

Add attachments 2017-07-05 09:18:50 -04:00			`require_relative "create_users_migration"`
Test blobs with real db backend 2017-07-01 06:47:13 -04:00
Added rubocop / codeclimate config and fixed current offenses (#45) 2017-07-13 18:09:56 -04:00			`ActiveRecord::Base.establish_connection(adapter: "sqlite3", database: ":memory:")`
Refactor migration to move migrations paths to connection Rails has some support for multiple databases but it can be hard to handle migrations with those. The easiest way to implement multiple databases is to contain migrations into their own folder ("db/migrate" for the primary db and "db/seconddb_migrate" for the second db). Without this you would need to write code that allowed you to switch connections in migrations. I can tell you from experience that is not a fun way to implement multiple databases. This refactoring is a pre-requisite for implementing other features related to parallel testing and improved handling for multiple databases. The refactoring here moves the class methods from the `Migrator` class into it's own new class `MigrationContext`. The goal was to move the `migrations_paths` method off of the `Migrator` class and onto the connection. This allows users to do the following in their `database.yml`: ``` development: adapter: mysql2 username: root password: development_seconddb: adapter: mysql2 username: root password: migrations_paths: "db/second_db_migrate" ``` Migrations for the `seconddb` can now be store in the `db/second_db_migrate` directory. Migrations for the primary database are stored in `db/migrate`". The refactoring here drastically reduces the internal API for migrations since we don't need to pass `migrations_paths` around to every single method. Additionally this change does not require any Rails applications to make changes unless they want to use the new public API. All of the class methods from the `Migrator` class were `nodoc`'d except for the `migrations_paths` and `migrations_path` getter/setters respectively. 2018-01-10 10:25:13 -05:00			`ActiveRecord::Base.connection.migration_context.migrate`
Fix the migration class name Due to Active Support auto loading feature, the migration class shouldn't be name-spaced under the `ActiveStorage` constant, otherwise, running the migrations would throw an error. 2017-07-06 15:53:51 -04:00			`ActiveStorageCreateUsers.migrate(:up)`