![]() ![]() One thing that I found unique about Sequel (and of course I hit an error to figure it out), is that the database must first be created before you attempt to connect to connect Sequel to the database. Within your application.rb file, you will need to require ‘sequel’, just as you would with ActiveRecord. You will need to install the gem by running $ bundle install in your terminal. To do this, go to your Gemfile and add gem ‘sequel’. In order to use Sequel, you must first install the gem to your project. Sequel currently supports the following database types: ADO, Amalgalite, IBM_DB, JDBC, MySQL, Mysql2, ODBC, Oracle, PostreSQL, SQLAnywhere, SQLite3, and TinyTDS. Sequel allows you to run migrations, queries, and manipulate the database, just as ActiveRecord does. Sequel is a Ruby gem that functions as a “simple, flexible, and powerful SQL database access toolkit.” In other words, it is comparable to the widely used ActiveRecord gem. We shall see what it is by the time I’ve finished this blog post. While working with it, I really enjoyed one aspect which softened my opinion a bit. My first instinct was to wonder why anybody would ever use this gem over ActiveRecord. My opinion on Sequel is still up in the air. One of these tools was Sequel, which is what I’ll be writing about today.įor my challenge, I was required to use Sequel instead of ActiveRecord and boy was it a challenge. I gained invaluable experience building with tools/frameworks I don’t know I would have every known existed and/or used. ![]() Practice makes perfect, so the more I get, the more confident and comfortable I’ll be the following time. I was super excited to even get the opportunity, because this is my second coding challenge of my job search. I was required to build a RESTful API with Ruby with one big catch: no Rails. On Friday, I was given a take home coding assessment. ![]()
0 Comments
Leave a Reply. |