sinatra-sequel icon indicating copy to clipboard operation
sinatra-sequel copied to clipboard

Sinatra extension that adds Sequel ORM features, database config, and database migrations

Results 13 sinatra-sequel issues
Sort by recently updated
recently updated
newest added

We still see this. `Sinatra::Base#options is deprecated and will be removed, use #settings instead.`

At the time of writing the last commit was in 2013, that's 4 years ago. The lastest commit to the Sinatra project itself was 13 hours ago. Is this project...

I'm using the `sinatra-sequel` gem inside a Docker container using this `Dockerfile`: ``` FROM ruby:2.3.0 RUN apt-get update &&\ apt-get install -y postgresql-client RUN mkdir -p /usr/src/app WORKDIR /usr/src/app #...

Warning when using `sinatra-sequel` since 2011 (see issue#5 originally opened by @cactus): ``` Sinatra::Base#options is deprecated and will be removed, use #settings instead. ```

I get this first time I run migrations. It works 2nd time though. ``` /home/jchan/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/mysql2-0.4.4/lib/mysql2/client.rb:107:in `_query': Mysql2::Error: BLOB/TEXT column 'name' used in key specification without a key length (Sequel::DatabaseError) from...

When I use a Sinatra::Base class to create my App like for example: myapp.rb ``` require 'sinatra/base' require 'sinatra/sequel' class MyApp < Sinatra::Base configure do set :sessions, true set :database,...

use table_exists? to detect if migration table should be created to avoid SQLite3::SQLException: index migrations_name_index already exists

I'm getting this error using MySQL 14.14, ruby mysql gem 2.8.1, sinatra-sequel 0.9.0: ``` /gems/sequel-3.23.0/lib/sequel/adapters/mysql.rb:200:in `query': Mysql::Error: BLOB/TEXT column 'name' used in key specification without a key length (Sequel::DatabaseError) from...

a database for each env