fat_table 0.2.7 → 0.3.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: 4c545f67e0496d870adfa57ec7bdbe6b8b0b5af8
-  data.tar.gz: 59a03a6b61876344facf14a5ec6a65bf47300b33
+SHA256:
+  metadata.gz: 3cff489c9e921eff2138fb44b260b96d548819b7ee1479f9bf89675f2199c9ea
+  data.tar.gz: 7ad900e458b8d95baaf8044a4d25e742b1796ae9677d9f667180f034760e8a55
 SHA512:
-  metadata.gz: ec213d073ddad80a8167b05e3a0fad399886c605a41160c41c428e2664f030f862c159bb077558521ce1bb32fd004527ec540fb8e3e51906d993712b9be0abeb
-  data.tar.gz: e160d5bacf83be72296029835f22412565e27649c097869f2653b86b8b23a65d0d541593349221fde1c5b6dc381785b0d192f3cd434269c6a2647362f433cfdc
+  metadata.gz: 061ddacf0132d62f7d428f513c7a14277a4668c5a37148f80ef87dc484163ee4c001164e20a854d61761f21d6df025a700171e85c33e4f53c548014d7804b4e2
+  data.tar.gz: 11351e7a9c73624c4395960c226733b2c1ccaa126f0a0f1c2eee042b83f5adacbcea52e303b8566d5746c16648e202441d5df2216cc818799864600c7ee3bf69

data/.gitignore

@@ -13,6 +13,7 @@
 .rspec_status
 /README.pdf
 /README.tex
+/README.md
 /README.synctex.gz
 /_minted*
 /auto/
@@ -24,3 +25,4 @@
 /GRTAGS
 /GTAGS
 /TAGS
+/README.pyg

data/.rubocop.yml

@@ -0,0 +1,18 @@
+inherit_gem:
+    rubocop-shopify: rubocop.yml
+require: rubocop-rspec
+require: rubocop-performance
+
+AllCops:
+  TargetRubyVersion: 2.7
+  Exclude:
+    - 'test/tmp/**/*'
+    - 'vendor/bundle/**/*'
+
+Style/MethodCallWithArgsParentheses:
+  Exclude:
+    - '**/Gemfile'
+
+Style/ClassAndModuleChildren:
+  Exclude:
+    - 'test/**/*'

data/.travis.yml

@@ -2,8 +2,9 @@ language: ruby
 before_install:
   - sudo apt-get -qq update
   - sudo apt-get install -y texlive-latex-base texlive-latex-recommended
-before_script:
-  - createdb -U travis travis
+  - gem install pg
+# before_script:
+#   - createdb -U travis travis
 after_failure:
   - "pwd"
   - "cat ./spec/tmp/latex.err"
@@ -13,7 +14,9 @@ bundler_args: --without debug
 services:
   - postgresql
 rvm:
-  - 2.2.2
-  - 2.3
   - 2.4
+  - 2.5
+  - 2.6
+  - 2.7
   - ruby-head
+  - truffleruby

data/.yardopts

@@ -1 +1,5 @@
---no-private lib/**/*.rb --markup=markdown --main=README.rdoc - README.rdoc
+--no-private lib/**/*.rb
+--markup=markdown
+--main=md/README.md
+-
+md/README.md

data/Gemfile

@@ -1,4 +1,6 @@
 source 'https://rubygems.org'
 
+gem 'rubocop-shopify', require: false
+
 # Specify your gem's dependencies in fat_table.gemspec
 gemspec

data/README.org

@@ -2,7 +2,11 @@
 #+LATEX_HEADER: \usepackage[margin=0.75in]{geometry}
 
 #+BEGIN_COMMENT
+This is for markdown output:
+
 [![Build Status](https://travis-ci.org/ddoherty03/fat_table.svg?branch=master)](https://travis-ci.org/ddoherty03/fat_table)
+
+The following is for org.
 #+END_COMMENT
 
 [[https://travis-ci.org/ddoherty03/fat_table.svg?branch=master]]
@@ -12,7 +16,7 @@
 ~FatTable~ is a gem that treats tables as a data type. It provides methods for
 constructing tables from a variety of sources, building them row-by-row,
 extracting rows, columns, and cells, and performing aggregate operations on
-columns. It also provides as set of SQL-esque methods for manipulating table
+columns. It also provides a set of SQL-esque methods for manipulating table
 objects: ~select~ for filtering by columns or for creating new columns, ~where~
 for filtering by rows, ~order_by~ for sorting rows, ~distinct~ for eliminating
 duplicate rows, ~group_by~ for aggregating multiple rows into single rows and
@@ -31,7 +35,7 @@ no-ops.
 ~FatTable~ can be used to perform operations on data that are naturally best
 conceived of as tables, which in my experience is quite often. It can also serve
 as a foundation for providing reporting functions where flexibility about the
-output medium can be quite useful. Finally ~FatTable~ can be used within Emacs
+output medium can be useful. Finally ~FatTable~ can be used within Emacs
 ~org-mode~ files in code blocks targeting the Ruby language. Org mode tables are
 presented to a ruby code block as an array of arrays, so ~FatTable~ can read
 them in with its ~.from_aoa~ constructor. A ~FatTable~ table output as an array
@@ -40,17 +44,6 @@ buffer as an org-table, ready for processing by other code blocks.
 
 * Installation
 
-** Prerequisites
-The ~fat_table~ gem depends on several libraries being available for building,
-mostly those concerned with accessing databases.  On an ubuntu system, the
-following packages should be installed before you install the ~fat_table~ gem:
-
-- ruby-dev
-- build-essential
-- libsqlite3-dev
-- libpq-dev
-- libmysqlclient-dev
-
 ** Installing the gem
 
 Add this line to your application's Gemfile:
@@ -76,7 +69,7 @@ Or install it yourself as:
 
 ~FatTable~ provides table objects as a data type that can be constructed and
 operated on in a number of ways. Here's a quick example to illustrate the use of
-the main features of ~FatTable~. See the detailed explanations further on down.
+~FatTable~. See the detailed explanations further on down.
 
 #+HEADER: :colnames no :session readme :hlines yes :wrap EXAMPLE :exports both
 #+BEGIN_SRC ruby
@@ -165,11 +158,12 @@ the main features of ~FatTable~. See the detailed explanations further on down.
 
 ** A Word About the Examples
 
-When you install the ~fat_table~ gem, you have access to a program ~ft_console~
+When you install the ~fat_table~ gem, you have access to a program ~ft_console~,
 which opens a ~pry~ session with ~fat_table~ loaded and the tables used in the
 examples in this ~README~ defined as instance variables so you can experiment
 with them. Because they are defined as instance variables, you have to write
-~tab1~ as ~@tab1~ in ~ft_console~, but otherwise the examples should work.
+~tab1~ as ~@tab1~ in ~ft_console~, but otherwise the examples should work as
+shown in this ~README~.
 
 The examples in this ~README~ file are executed as code blocks within the
 ~README.org~ file, so they typically end with a call to ~.to_aoa~. That causes
@@ -231,7 +225,7 @@ locals: _  __  _dir_  _ex_  _file_  _in_  _out_  _pry_  lib  str  version
 [4] pry(main)>
 #+END_EXAMPLE
 
-And if you use ~.to_term~, you can see the effect of the color formatting
+If you use ~puts table.to_term~, you can see the effect of the color formatting
 directives.
 
 ** Anatomy of a Table
@@ -478,16 +472,16 @@ This example illustrates several things:
    where the number of shares is greater than 500.  More on that later.
 4. ~FatTable~ passes back to org-mode an array of arrays using the ~.to_aoa~
    method. In an ~org-mode~ buffer, these are rendered as tables. We'll often
-   apply ~.to_aoa~ at the end of example blocks to render the results inside
-   this ~README.org~ file. As we'll see below, this method can also take a block
-   to which formatting directives and footers can be attached.
+   apply ~.to_aoa~ at the end of example blocks in this ~README~ to render the
+   results as a table inside this file. As we'll see below, ~.to_aoa~ can also
+   take a block to which formatting and footer directives can be attached.
 
 *** From Arrays of Hashes
 
 A second ruby data structure that can be used to initialize a ~FatTable~ table
 is an array of ruby Hashes. Each hash represents a row of the table, and the
-headers of the table are take from the keys of the hashes. Accordingly, all the
-hashes should have the same keys.
+headers of the table are taken from the keys of the hashes. Accordingly, all the
+hashes must have the same keys.
 
 This same method can in fact take an array of any objects that can be converted
 to a Hash with the ~#to_h~ method, so you can use an array of your own objects
@@ -517,40 +511,38 @@ tab = FatTable.from_aoh(aoh)
 #+END_SRC
 
 Notice, again, that the values can either be ruby objects, such as ~Date.today~,
-or strings that can parsed into one of the permissible column types.
+or strings that can be parsed into one of the permissible column types.
 
 *** From SQL queries
 
-Another way to initialize a ~FatTable~ table is with the results of a SQL query.
-~FatTable~ uses the ~sequel~ gem to query databases. You must first set the
-database parameters to be used for the queries.
+Another way to initialize a ~FatTable~ table is with the results of a SQL
+query.  Before you can connect to a database, you need to make sure that the required
+adapter for your database is installed.  ~FatTable~ uses the ~sequel~ gem
+under the hood, so any database that it supports can be used.  For example, if
+you are accessing a Postgres database, you must install the ~pg~ gem with
+
+#+begin_src sh
+$ gem install pg
+#+end_src
+
+You must first set the database parameters to be used for the queries.
 
 #+BEGIN_SRC ruby
   # This automatically requires sequel.
   require 'fat_table'
-  FatTable.set_db(driver: 'Pg',
+  FatTable.connect(adapter: 'postgres',
                   database: 'XXX_development',
-                  user: 'dtd',
-                  password: 'slflpowert',
-                  host: 'localhost',
-                  socket: '/tmp/.s.PGSQL.5432')
+                  user: 'ken',
+                  password: 'imsecret',
+                  host: 'db.lan')
   tab = FatTable.from_sql('select * from trades;')
 #+END_SRC
 
-Some of the parameters to the ~.set_db~ function have defaults. The driver
-defaults to ~'Pg'~ for postgresql and the socket defaults to
-~/tmp/.s.PGSQL.5432~ if the host is 'localhost', which it is by default. If the
-host is not ~'localhost'~, the dsn uses a port rather than a socket and defaults
-to port ~'5432'~. While user and password default to nil, the database parameter
-is required.
-
-The ~.set_db~ function need only be called once, and the database handle it
-creates will be used for all subsequent ~.from_sql~ calls until ~.set_db~ is
-called again.
-
-Alternatively, you can build the ~Sequel~ connection with ~Sequel.connect~ or
-with adapter-specific ~Sequel~ connection methods and let ~FatTable~ know to use
-that connection:
+The arguments to ~connect~ are simply passed on to ~sequel~'s connect method, so
+any set of arguments that work for it should work for ~connect~. Alternatively,
+you can build the ~Sequel~ connection directly with ~Sequel.connect~ or with
+adapter-specific ~Sequel~ connection methods and let ~FatTable~ know to use that
+connection:
 
 #+BEGIN_SRC ruby
   require 'fat_table'
@@ -561,8 +553,15 @@ that connection:
 Consult ~Sequel's~ documentation for details on its connection methods.
 [[http://sequel.jeremyevans.net/rdoc/files/doc/opening_databases_rdoc.html]]
 
+The ~.connect~ function need only be called once, and the database handle it
+creates will be used for all subsequent ~.from_sql~ calls until ~.connect~ is
+called again.
+
 *** Marking Groups in Input
 
+~FatTable~ tables has a concept of "groups" of rows that play a role in many of
+the methods for operating on them as explained [[Groups][below]].
+
 The ~.from_aoa~ and ~.from_aoh~ functions take an optional keyword parameter
 ~hlines:~ that, if set to ~true~, causes them to mark group boundaries in the
 table wherever a row Array (for ~.from_aoa~) or Hash (for ~.from_aoh~) is
@@ -582,6 +581,7 @@ beginning with something like '~|---~'. The ~.from_org_...~ functions always
 recognizes hlines in the input, so it takes no ~hlines:~ keyword parameter.
 
 ** Accessing Parts of Tables
+
 *** Rows
 
 A ~FatTable~ table is an Enumerable, yielding each row of the table as a Hash
@@ -637,6 +637,7 @@ operation, which mutates the receiver table by removing its group boundaries.
 Second, because each operation returns a ~FatTable::Table~ object, the
 operations are chainable.
 
+<<Groups>>
 Third, ~FatTable::Table~ objects can have "groups" of rows within the table.
 These can be decorated with hlines and group footers on output. Some of these
 operations result in marking group boundaries in the result table, others remove
@@ -767,17 +768,18 @@ symbol representing an existing column, which has the effect of renaming an
 existing column, or (2) a string representing a ruby expression for the value of
 a new column.
 
-Within the string expression, the names of existing or already-specified columns
-are available as local variables, as well as the instance variables '@row' and
-'@group'. So for our example table, the string expressions for new columns have
-access to local variables ~ref~, ~date~, ~code~, ~price~, ~g10~, ~qp10~,
+Within the string expression, the names of existing or already-specified
+columns are available as local variables.  In addition the instance variables
+'@row' and '@group' are available as the row number and group number of the
+new value. So for our example table, the string expressions for new columns
+have access to local variables ~ref~, ~date~, ~code~, ~price~, ~g10~, ~qp10~,
 ~shares~, ~lp~, ~qp~, ~iplp~, and ~ipqp~ as well as the instance variables
 ~@row~ and ~@group~. The local variables are set to the values of the cell in
-their respective columns for each row in the input table and the instance
-variables are set the number of the current row and group respectively.
+their respective columns for each row in the input table, and the instance
+variables are set the number of the current row and group number respectively.
 
-For example, if we want to rename the ~:date~ column and add a new column to
-compute the cost of shares, we could do the following:
+For example, if we want to rename the ~traded_on~ column to ~:date~ and add a
+new column to compute the cost of shares, we could do the following:
 
 #+HEADER: :colnames no :session readme :hlines yes :wrap EXAMPLE :exports both
 #+BEGIN_SRC ruby
@@ -959,28 +961,21 @@ You can sort a table on any number of columns with ~order_by~. The ~order_by~
 method takes any number of symbol arguments for the columns to sort on. If you
 specify more than one column, the sort is performed on the first column, then
 all columns that are equal with respect to the first column are sorted by the
-second column, and so on. All columns of the input table are included in the
-output.
+second column, and so on. Ordering is done is ascending order for each of the
+columns, but can be reversed by adding a '!' to the end a symbol argument.
+All columns of the input table are included in the output.
 
-Let's sort our table first by ~:code~, then by ~:date~.
+Let's sort our table first by ~:code~, then in reverse order of ~:date~.
 
 #+HEADER: :colnames no :session readme :hlines yes :wrap EXAMPLE :exports both
 #+BEGIN_SRC ruby
-  tab1.order_by(:code, :date) \
+  tab1.order_by(:code, :date!) \
     .to_aoa
 #+END_SRC
 
-#+BEGIN_EXAMPLE
+#+begin_EXAMPLE
 | Ref  |       Date | Code | Price | G10 | QP10 | Shares |   Lp |    Qp |   Iplp |   Ipqp |
 |------+------------+------+-------+-----+------+--------+------+-------+--------+--------|
-| T001 | 2016-11-01 | P    |   7.7 | T   | F    |    100 |   14 |    86 | 0.2453 | 0.1924 |
-| T002 | 2016-11-01 | P    |  7.75 | T   | F    |    200 |   28 |   172 | 0.2453 | 0.1924 |
-| T003 | 2016-11-01 | P    |   7.5 | F   | T    |    800 |  112 |   688 | 0.2453 | 0.1924 |
-| T003 | 2016-11-01 | P    |   7.5 | F   | T    |    800 |  112 |   688 | 0.2453 | 0.1924 |
-| T008 | 2016-11-01 | P    |  7.65 | F   | F    |   2771 |  393 |  2378 | 0.2453 | 0.1924 |
-| T009 | 2016-11-01 | P    |   7.6 | F   | F    |   9550 | 1363 |  8187 | 0.2453 | 0.1924 |
-| T010 | 2016-11-01 | P    |  7.55 | F   | T    |   3175 |  451 |  2724 | 0.2453 | 0.1924 |
-|------+------------+------+-------+-----+------+--------+------+-------+--------+--------|
 | T011 | 2016-11-02 | P    | 7.425 | T   | F    |    100 |   14 |    86 | 0.2453 | 0.1924 |
 | T012 | 2016-11-02 | P    |  7.55 | F   | F    |   4700 |  677 |  4023 | 0.2453 | 0.1924 |
 | T012 | 2016-11-02 | P    |  7.55 | F   | F    |   4700 |  677 |  4023 | 0.2453 | 0.1924 |
@@ -989,12 +984,20 @@ Let's sort our table first by ~:code~, then by ~:date~.
 | T015 | 2016-11-02 | P    |  7.75 | F   | F    |    500 |   72 |   428 | 0.2453 | 0.1924 |
 | T016 | 2016-11-02 | P    |  8.25 | T   | T    |    100 |   14 |    86 | 0.2453 | 0.1924 |
 |------+------------+------+-------+-----+------+--------+------+-------+--------+--------|
+| T001 | 2016-11-01 | P    |   7.7 | T   | F    |    100 |   14 |    86 | 0.2453 | 0.1924 |
+| T002 | 2016-11-01 | P    |  7.75 | T   | F    |    200 |   28 |   172 | 0.2453 | 0.1924 |
+| T003 | 2016-11-01 | P    |   7.5 | F   | T    |    800 |  112 |   688 | 0.2453 | 0.1924 |
+| T003 | 2016-11-01 | P    |   7.5 | F   | T    |    800 |  112 |   688 | 0.2453 | 0.1924 |
+| T008 | 2016-11-01 | P    |  7.65 | F   | F    |   2771 |  393 |  2378 | 0.2453 | 0.1924 |
+| T009 | 2016-11-01 | P    |   7.6 | F   | F    |   9550 | 1363 |  8187 | 0.2453 | 0.1924 |
+| T010 | 2016-11-01 | P    |  7.55 | F   | T    |   3175 |  451 |  2724 | 0.2453 | 0.1924 |
+|------+------------+------+-------+-----+------+--------+------+-------+--------+--------|
 | T004 | 2016-11-01 | S    |  7.55 | T   | F    |   6811 |  966 |  5845 | 0.2453 | 0.1924 |
 | T005 | 2016-11-01 | S    |   7.5 | F   | F    |   4000 |  572 |  3428 | 0.2453 | 0.1924 |
 | T006 | 2016-11-01 | S    |   7.6 | F   | T    |   1000 |  143 |   857 | 0.2453 | 0.1924 |
 | T006 | 2016-11-01 | S    |   7.6 | F   | T    |   1000 |  143 |   857 | 0.2453 | 0.1924 |
 | T007 | 2016-11-01 | S    |  7.65 | T   | F    |    200 |   28 |   172 | 0.2453 | 0.1924 |
-#+END_EXAMPLE
+#+end_EXAMPLE
 
 The interesting thing about ~order_by~ is that, while it ignores groups in its
 input, it adds group boundaries in the output table at those rows where the sort
@@ -1039,8 +1042,10 @@ the value is a symbol for one of several aggregating methods that
 to the :price column so that the output shows the average price in each group.
 The ~:shares~, ~:lp~, and ~:qp~ columns are summed, and the ~:any?~ aggregate is
 applied to one of the boolean fields, that is, it is ~true~ if any of the values
-in that column are ~true~. The column names in the output of the aggregated
-columns have the name of the aggregating method pre-pended to the column name.
+in that column are ~true~.
+
+Note that the column names in the output of the aggregated columns have the
+name of the aggregating method pre-pended to the column name.
 
 Here is a list of all the aggregate methods available.  If the description
 restricts the aggregate to particular column types, applying it to other types
@@ -1309,6 +1314,7 @@ table where the join expression is satisfied and augmented with nils otherwise.
 Finally, a cross join outputs every row of ~tab_a~ augmented with every row of
 ~tab_b~, in other words, the Cartesian product of the two tables. If ~tab_a~ has
 ~N~ rows and ~tab_b~ has ~M~ rows, the output table will have ~N * M~ rows.
+So be careful lest you consume all your computer's memory.
 
 #+HEADER: :colnames no :session readme :hlines yes :wrap EXAMPLE :exports both
 #+BEGIN_SRC ruby
@@ -1346,10 +1352,10 @@ Finally, a cross join outputs every row of ~tab_a~ augmented with every row of
 
 *** Set Operations
 
-~FatTable~ can perform several set operations on tables. In order for two tables
-to be used this way, they must have the same number of columns with the same
-types or an exception will be raised. We'll call two tables that qualify for
-combining with set operations "set-compatible."
+~FatTable~ can perform several set operations on pairs of tables. In order for
+two tables to be used this way, they must have the same number of columns with
+the same types or an exception will be raised. We'll call two tables that
+qualify for combining with set operations "set-compatible."
 
 We'll use the following two set-compatible tables in the examples. They each
 have some duplicates and some group boundaries so you can see the effect of the
@@ -1761,9 +1767,9 @@ but ruby data structures, and for them, things such as alignment are irrelevant.
      array of array,
 
 These are all implemented by classes that inherit from ~FatTable::Formatter~
-class by defining about a dozen methods that get called at various places during
-the construction of the output table. The idea is that more classes can be
-defined by adding additional classes.
+class by defining about a dozen methods that get called at various places
+during the construction of the output table. The idea is that more output
+formats can be defined by adding additional classes.
 
 *** Table Locations
 

data/README.rdoc

@@ -485,7 +485,7 @@ Another way to initialize a +FatTable+ table is with the results of a SQL query.
 database parameters to be used for the queries.
 
   require 'fat_table'
-  FatTable.set_db(driver: 'Pg',
+  FatTable.connect(driver: 'Pg',
                   database: 'XXX_development',
                   user: 'dtd',
                   password: 'slflpowert',
@@ -493,15 +493,15 @@ database parameters to be used for the queries.
                   socket: '/tmp/.s.PGSQL.5432')
   tab = FatTable.from_sql('select * from trades;')
 
-Some of the parameters to the +.set_db+ function have defaults. The driver
+Some of the parameters to the +.connect+ function have defaults. The driver
 defaults to 'Pg' for postgresql and the socket defaults to +/tmp/.s.PGSQL.5432+
 if the host is 'localhost', which it is by default. If the host is not
 'localhost', the dsn uses a port rather than a socket and defaults to port
 '5432'. While user and password default to nil, the database parameter is
 required.
 
-The +.set_db+ function need only be called once, and the database handle it
-creates will be used for all subsequent +.from_sql+ calls until +.set_db+ is
+The +.connect+ function need only be called once, and the database handle it
+creates will be used for all subsequent +.from_sql+ calls until +.connect+ is
 called again.
 
 === Marking Groups in Input

data/fat_table.gemspec

@@ -1,7 +1,6 @@
 lib = File.expand_path('../lib', __FILE__)
 $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
 require 'fat_table/version'
-require 'fat_table/patches'
 
 Gem::Specification.new do |spec|
   spec.name          = 'fat_table'
@@ -10,7 +9,7 @@ Gem::Specification.new do |spec|
   spec.email         = ['ded-law@ddoherty.net']
 
   spec.summary       = 'Provides tools for working with tables as a data type.'
-  spec.description   = <<-DESC.strip_heredoc
+  spec.description   = <<-DESC
     FatTable is a gem that treats tables as a data type. It provides methods for
     constructing tables from a variety of sources, building them row-by-row,
     extracting rows, columns, and cells, and performing aggregate operations on
@@ -64,21 +63,22 @@ Gem::Specification.new do |spec|
   spec.require_paths = ['lib']
   spec.metadata['yard.run'] = 'yri' # use "yard" to build full HTML docs.
 
-  spec.add_development_dependency 'bundler', '~> 1.14'
+  spec.add_development_dependency 'bundler'
   spec.add_development_dependency 'byebug'
   spec.add_development_dependency 'pry'
   spec.add_development_dependency 'pry-byebug'
   spec.add_development_dependency 'pry-doc'
-  spec.add_development_dependency 'rake', '~> 10.0'
+  spec.add_development_dependency 'ruby_jard'
+  spec.add_development_dependency 'rake', '~> 13.0'
   spec.add_development_dependency 'redcarpet'
   spec.add_development_dependency 'rspec', '~> 3.0'
+  spec.add_development_dependency 'rubocop-rspec'
+  spec.add_development_dependency 'rubocop-performance'
   spec.add_development_dependency 'simplecov'
 
   spec.add_runtime_dependency 'activesupport', '>3.0'
-  spec.add_runtime_dependency 'fat_core', '~> 4.0', '>= 4.1'
-  spec.add_runtime_dependency 'mysql2'
-  spec.add_runtime_dependency 'pg'
+  spec.add_runtime_dependency 'fat_core', '>= 4.1'
   spec.add_runtime_dependency 'rainbow'
   spec.add_runtime_dependency 'sequel'
-  spec.add_runtime_dependency 'sqlite3'
+  spec.add_runtime_dependency 'gem-path'
 end