brick | generate models , views , controllers , and routes | Application Framework library

Add Brick to your Gemfile and bundle. ` gem 'brick' `. To test things, configure database.yml to use any popular adapter of your choosing — Postgres, MySQL, Oracle, Microsoft SQL Server, or Sqlite3, and point to an existing relational database. Then from within bin/rails c attempt to reference a model by what its normal name might be. For instance, if you have a plants table then just type Plant.count and see that automatically a model is built out on-the-fly and the count for this plants table is shown. If you similarly have products that relates to categories with a foreign key then notice that by referencing Category the gem builds out a model which has a has_many association called :products. Without writing any code these associations are all wired up as long as you have proper foreign keys in place. Even if your table and column names do not follow Rails' conventions, everything still works because as models are built out then `self.table_name = ` and `self.primary_key = ` entries are provided as needed. Likewise, belongs_to and has_many associations will indicate which foreign_key and class_name to use whenever anything is non-standard. Everything just works.
Add Brick to your Gemfile and bundle. ` gem 'brick' `
To test things, configure database.yml to use any popular adapter of your choosing — Postgres, MySQL, Oracle, Microsoft SQL Server, or Sqlite3, and point to an existing relational database. Then from within bin/rails c attempt to reference a model by what its normal name might be. For instance, if you have a plants table then just type Plant.count and see that automatically a model is built out on-the-fly and the count for this plants table is shown. If you similarly have products that relates to categories with a foreign key then notice that by referencing Category the gem builds out a model which has a has_many association called :products. Without writing any code these associations are all wired up as long as you have proper foreign keys in place.
You should be able to set up the test database for Postgres with:.
If you’re on Linux:.
Oracle is the third most popular database solution used for Rails projects in production, so it only makes sense to have support for this in The Brick. Starting with version 1.0.69 this was added, offering full compatibility for all Brick features. This can run on Linux, Windows, and Mac. One important caveat for those with Apple M1 or M2 machines is that the low-level Ruby driver which we rely upon will NOT function natively on Apple Silicon, so on an M1 or M2 machine you will have to use the Rosetta emulator to run Ruby and your entire Rails app. In the future when an Apple Silicon version of Oracle Instant Client ships then everything can work natively.
MSSQL is the fifth most popular database solution used for Rails projects in production, so it only makes sense to have support for this in The Brick. Starting with version 1.0.70 this was added, offering full compatibility for all Brick features. The client library can run on Linux, Windows, and Mac.