Sequel
Mongoid
Our great sponsors
Sequel | Mongoid | |
---|---|---|
19 | 5 | |
4,612 | 3,889 | |
- | 0.1% | |
8.8 | 9.3 | |
5 days ago | 6 days ago | |
Ruby | Ruby | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Sequel
-
Ask HN: What are some examples of elegant software?
Sequel [1], the Ruby ORM. It's rock-solid, provides similar abstractions to Active Record but feels much better thought out, and it has great docs.
Also, at any point in time, it's likely to have zero open issues and zero open pull requests, which is pretty impressive for a project of its size.
-
"ORMs have a special place in my heart, not entirely unlike Brutus and Caesar: a dear friend who betrays you and leaves you to die a slow, painful death." – Taming SQL and ORMs with sqlc
The most excellent ORM I've ever worked with was sequel for ruby. The only time I felt the tool wasn't working against me, and gave me access to all those advanced db features ORM are so good at hiding from you.
- Migrating from SQLite to PostgreSQL
-
It is OK for your open source project not to have a public bug tracker
As a developer, though, it's a bit problematic for users reporting issues. Yes, it is beneficial, I get it, but ... I just lack the time to really go towards fixing most of the problems. I even have my own bug reports for my own code and many of these just are never resolved. It's just not manageable after a certain amount, and if you have too many projects. And when you lack time, you don't really go through the issues either, so they just compound without ever being resolved. Some projects handle issue request really very well (jeremy's sequel, for instance https://github.com/jeremyevans/sequel), but it takes a lot of discipline to do so too. I don't have that discipline, so it's all just more and more on the todo list ... :P
-
Roda: Simplicity, Reliability, Extensibility & Performance by Jeremy Evans
Sequel
-
Where is Ruby Headed in 2021?
I've never used Rails. I used Sinatra in the early days and over the last 8 years I've used Roda[0] and Sequel[1].
Our stack is front-end heavy with a very mature JS framework and the back-end is mostly an API server. Databases range from SQLite to Postgres.
Development is usually done on SQLite and staging / production on Postgres. Quite a few projects with SQLite DB in production as well.
-
Async Ruby
It seems that Active Record compatibility is being discussed here. It's kind of cool that all it took for Sequel to be async-compatible was to replace Thread.current with Fiber.current.
-
Little known vulnerability with SQL wrappers
The problem that exposes is that of mass assignment. For example, the Ruby ORM library Sequel goes to some lengths to deal with it - but most popular frameworks are in a similar boat.
-
Best programming language for a db app?
Till date, I've only found Ruby's ORM Sequel and Go's ORM GORM to be the most versatile, flexible and suitable for all the use cases I throw at them.
-
Does Anyone use Sinatra in Production?
Yes we use it in production with Sequel. It's been great though we're now switching over to Roda
Mongoid
-
How a routine gem update ended up creating $73k worth of subscriptions
I'm guessing it's 7.1 that broke it ?
-
A routine gem update ended up creating $73k worth of subscriptions
The changelog for 7.1 (https://github.com/mongodb/mongoid/blob/master/docs/release-...) even explicitly call this out as a breaking change:
*Breaking change:* In Mongoid 7.1, when condition methods are invoked on a
The mongoid repository (https://github.com/mongodb/mongoid) doesn't have issues turned on and instead points people to JIRA. That's one way to avoid users reporting issues like this - I'd see JIRA and "nope" right out.
-
Unable to build and deploy Rails 6.0.4.1 app on heroku - Throws gyp verb cli error
source 'https://rubygems.org' git_source(:github) { |repo| "https://github.com/#{repo}.git" } ruby '2.7.3' # Bundle edge Rails instead: gem 'rails', github: 'rails/rails' gem 'rails', '~> 6.0.3', '>= 6.0.3.7' gem 'mongoid', git: 'https://github.com/mongodb/mongoid.git' # Use Puma as the app server gem 'puma', '~> 4.1' # Use SCSS for stylesheets gem 'sass-rails', '>= 6' # Transpile app-like JavaScript. Read more: https://github.com/rails/webpacker gem 'webpacker', '~> 4.0' # Turbolinks makes navigating your web application faster. Read more: https://github.com/turbolinks/turbolinks gem 'turbolinks', '~> 5' # Build JSON APIs with ease. Read more: https://github.com/rails/jbuilder gem 'jbuilder', '~> 2.7' # Use Redis adapter to run Action Cable in production # gem 'redis', '~> 4.0' # Use Active Model has_secure_password # Use Active Storage variant # gem 'image_processing', '~> 1.2' gem 'axlsx' gem 'caxlsx_rails' #Bootstrap for UI gem 'bootstrap', '~> 5.1.0' gem 'bootstrap-timepicker-rails', '~> 0.1.3' gem 'bootstrap-select-rails', '~> 1.6', '>= 1.6.3' #JQuery Rails gem 'jquery-rails' gem 'rails_12factor', group: :production # Reduces boot times through caching; required in config/boot.rb gem 'bootsnap', '>= 1.4.2', require: false group :development, :test do # Call 'byebug' anywhere in the code to stop execution and get a debugger console gem 'byebug', platforms: [:mri, :mingw, :x64_mingw] end group :development do # Access an interactive console on exception pages or by calling 'console' anywhere in the code. gem 'web-console', '>= 3.3.0' gem 'listen', '~> 3.2' gem 'pry' # Spring speeds up development by keeping your application running in the background. Read more: https://github.com/rails/spring gem 'spring' gem 'spring-watcher-listen', '~> 2.0.0' end group :test do # Adds support for Capybara system testing and selenium driver gem 'capybara', '>= 2.15' gem 'selenium-webdriver' # Easy installation and use of web drivers to run system tests with browsers gem 'webdrivers' gem 'cucumber-rails', require: false gem 'database_cleaner' end # Windows does not include zoneinfo files, so bundle the tzinfo-data gem gem 'tzinfo-data', platforms: [:mingw, :mswin, :x64_mingw, :jruby] #HTTParty for RESTful API calls gem 'httparty' #Paperclip for storing files gem 'paperclip' gem "mongoid-paperclip", :require => "mongoid_paperclip" gem "letter_opener", :group => :development r
What are some alternatives?
ROM - Data mapping and persistence toolkit for Ruby
ActiveRecord
DataMapper
MongoMapper - A Ruby Object Mapper for Mongo
Hanami::Model - Ruby persistence framework with entities and repositories
Redis-Objects - Map Redis types directly to Ruby objects
Neo4j.rb - An active model wrapper for the Neo4j Graph Database for Ruby.
MongoModel - Ruby ORM for MongoDB (compatible with Rails 3)