yamldb/yaml_db

Rails 2.x support?

Closed this issue · 5 comments

(Meta-issue) Now that yaml_db has returned from a 2.5-year hiatus, does anyone think it should still support Rails 2.x? Please share your opinion.

The most recent issue reported against Rails 2 is #22 on 2011-06-02.

I'm a fan of supporting what rails/rails supports, with a 1 or 2 month lag, to give people time to migrate their applications.

lime commented

Following along right behind the Rails maintenance policy sounds like as good a principle as any. And seeing as 2.3.x isn't even receiving patches for severe security issues anymore, it doesn't sound like there's any need to reinstate support for Rails 2.

However, I would be open to the possibility if someone turns up in this issue and expresses the need. If no one does, then why bother? :)

Closing this as "wont fix". Sorry, Rails 2, but you're old.

Anyone needing Rails 2 support: feel free to make noise here in the future, but it may or may not get attention. You're probably better off trying an old version of yaml_db (0.1.x?).

czak commented

Let me share my story of the Rails2 branch.

A few weeks ago I reached a 10,000 free DB rows limit on Heroku, prompting me to either pay up or move out. This was for a Rails 2.3 app I wrote between 2009-2011. The app was consistently used by one person all these years so I was not going to abandon it, but I wasn't willing to invest much time or money into it.

I decided to dockerize it and - to keep a minimal footprint - opted for sqlite. This works fine.

Now for the fun part: I was glad to read about yaml_db's Rails2 branch. It worked without a glitch as a plugin (yeah vendor/plugins/ ... that brought some memories) and allowed me to migrate postgresql → sqlite in a few minutes.

So here's to you Rails2 branch, you have served me well. Sad to see you go 🍷