In the Rails 3 timeframe, I would like Rails to...

better support for non-relational databases

Rails ActiveRecord make easy to work with a relational SQL based database but there's a few support for the non-relational ones, like a document-oriented database. In many cases the non-relationals databases are a better choice.

273 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    philipefariasphilipefarias shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    4 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Matthew HigginsMatthew Higgins commented  ·   ·  Flag as inappropriate

        the api for a non-relational database should be different than a relational database, because the abilities of each are different. Why hide away the goodness of a relational database? I would consider a dedicated 'hash' based storage for memcached, tokyo cabinet, etc.

      • technoweenietechnoweenie commented  ·   ·  Flag as inappropriate

        One of the goals with Rails 3 is being ORM agnostic. There's work on documenting what ORMs need to be compatible with rails, and providing assistance for common libraries like Sequel and DataMapper to be completely compatible.

      • sonicpondsonicpond commented  ·   ·  Flag as inappropriate

        from your mouth to god's ears. in this case, perhaps wycat's ears.

        i couldn't agree more. for me, the dbm family, especially tokyo cabinet, is almost always the best tool for the job.

      Feedback and Knowledge Base