brick VS activerecord-cte

(While you were doing this article, I've been busy making bugfixes on the gem that looks at a database and auto-creates migrations.)

I'm on a path to try to recreate the Django admin interface in Rails. Many things work -- all BT and HM things, plus polymorphism / STI stuff / etc. And it's fast. But it doesn't yet have time series stuff or some other niceties that the Django one does.

Working VERY hard to have a lean and mean admin panel that can compare favorably to Django's.

Was able to fix that bug in the video when the ERD diagram had two lines when there should have been only one. So creating this example ended up revealing that bug and now has made The Brick that little bit stronger.

Using The Brick is an easy way to make many Rails 3.1 apps run under Ruby 2.7.8. In your Gemfile: gem 'brick' And at the very top of your application.rb add this line: require 'brick' And there's a good chance it will run fine. Note that nothing older than 3.1 will work. You got lucky to have an app that's right at the cutoff line!

I feel your pain, u/2called_chaos -- so much that after being totally fed up with this kind of unreliable faff, I fixed it in a gem I maintain! Here's a video demo of your exact setup. You can see it broken and then working after simply adding the gem:

-Lorin Curator of The Brick.

... and while waiting, unrelated, but if you haven't yet given my lockdown creation a whirl then please drop this into your current project and tell me what you think -- a gem called The Brick!

For the full story on auto-creating RESTful APIs for any Rails app, [go here](https://github.com/lorint/brick).

I want to bring 👽 my API thing 🚀 to your martian party with hopes that it could become a useful player amongst your universe of useful gems!

Yes -- the whole CTE functionality was originally put in by Vlado Cingel (author of the activerecord-cte gem), and included support for recursion. Before the PR was merged though the recursive part got pulled out, leaving just .with(). In the future a .with_recursive() method might be put in to fill this gap.

I listened to the Ruby Rogues podcast after a long while, and the main reason is that my friend Vlado was a guest on it with his cool and useful gem called activerecord-cte. One of the hosts said something like this: