postgres_key_value 0.2.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 2d46cdd5eefe2180f231e0696f3e9849fbd6d61b91f5b2a02066f5ef82ccbfc0
+  data.tar.gz: cdbf6755b5cba7283c47e351a8393123f9d3e4e6a0a437c521d51f734aec2739
+SHA512:
+  metadata.gz: 97a3f67306f9bf1008cdf014e3625638b280a693ef5bfe9aeeb38e86e7a60ce9ab865b58e2a77a62a6c79a32e133cce93c1afdc93bb57cfbf4eafc0ccde38b9d
+  data.tar.gz: f10a3162d5459bf1c3c636f01fc5a37d4ebf5ae56c43fd43c795c017519917285923a790f1f45fd6a333429d7730d9539a4266fb8f098d003101c9cfe4cd7a6c

data/.env.template

@@ -0,0 +1,6 @@
+DB_PASSWORD=DB_PASSWORD
+DB_USER=DB_USER
+DB_NAME=DB_NAME
+DEFAULT_DB_NAME=DEFAULT_DB_NAME
+DB_HOST=DB_HOST
+DB_PORT=DB_PORT

data/.github/workflows/main.yml

@@ -0,0 +1,39 @@
+---
+name: PostgresKeyValue
+
+on: [push, pull_request]  # yamllint disable-line rule:truthy
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    env:
+      DB_NAME: postgres
+      DB_USER: postgres
+      DB_PASSWORD: ${{ secrets.DB_PASSWORD }}
+      DB_HOST: localhost
+      DB_PORT: 5432
+    services:
+      postgres:
+        image: postgres
+        env:
+          POSTGRES_USER: postgres
+          POSTGRES_PASSWORD: ${{ secrets.DB_PASSWORD }}
+        ports:
+          - 5432:5432
+        options: >-
+          --health-cmd pg_isready
+          --health-interval 10s
+          --health-timeout 5s
+          --health-retries 5
+    steps:
+      - uses: actions/checkout@v2
+      - name: Set up Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 3.0.0
+      - name: Run the default task
+        run: |
+          gem install bundler -v 2.2.3
+          bundle install
+          bundle exec rake
+          bundle exec rake benchmark

data/.gitignore

@@ -0,0 +1,9 @@
+/.env
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/

data/.rubocop.yml

@@ -0,0 +1,3 @@
+AllCops:
+  TargetRubyVersion: '2.4'
+  NewCops: enable

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at ber@berk.es. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
+available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

data/Gemfile

@@ -0,0 +1,14 @@
+# frozen_string_literal: true
+
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in postgres_key_value.gemspec
+gemspec
+
+gem 'byebug'
+gem 'dotenv', '~> 2.7.6'
+gem 'minitest', '~> 5.0'
+gem 'rake', '~> 13.0'
+gem 'rubocop', '~> 0.80'
+
+gem 'pg', '~> 1'

data/Gemfile.lock

@@ -0,0 +1,48 @@
+PATH
+  remote: .
+  specs:
+    postgres_key_value (0.1.0)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    ast (2.4.2)
+    byebug (11.1.3)
+    dotenv (2.7.6)
+    minitest (5.15.0)
+    parallel (1.21.0)
+    parser (3.1.1.0)
+      ast (~> 2.4.1)
+    pg (1.3.3)
+    rainbow (3.1.1)
+    rake (13.0.6)
+    regexp_parser (2.2.1)
+    rexml (3.2.5)
+    rubocop (0.93.1)
+      parallel (~> 1.10)
+      parser (>= 2.7.1.5)
+      rainbow (>= 2.2.2, < 4.0)
+      regexp_parser (>= 1.8)
+      rexml
+      rubocop-ast (>= 0.6.0)
+      ruby-progressbar (~> 1.7)
+      unicode-display_width (>= 1.4.0, < 2.0)
+    rubocop-ast (1.16.0)
+      parser (>= 3.1.1.0)
+    ruby-progressbar (1.11.0)
+    unicode-display_width (1.8.0)
+
+PLATFORMS
+  x86_64-linux
+
+DEPENDENCIES
+  byebug
+  dotenv (~> 2.7.6)
+  minitest (~> 5.0)
+  pg (~> 1)
+  postgres_key_value!
+  rake (~> 13.0)
+  rubocop (~> 0.80)
+
+BUNDLED WITH
+   2.2.3

data/LICENSE.txt

@@ -0,0 +1,22 @@
+The MIT License (MIT)
+
+Copyright (c) 2022 Bèr Kessels
+
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,219 @@
+# PostgresKeyValue
+
+[![Ruby](https://github.com/berkes/postgres_key_value/actions/workflows/main.yml/badge.svg)](https://github.com/berkes/postgres_key_value/actions/workflows/main.yml)
+
+**Key-Value storage for Posgresql**
+
+Performant and simple key-value storage in Posgresql. With a Hash-like
+interface. Only dependency is pg gem.
+
+PostgresKeyValue tries to get out of your way, by being unopiniated small, and
+simple. 
+
+It works similar, but not compatible to, Hash. Some features from Hash are implemented, others
+deliberately omitted when they don't make sense or would make leaky abstractions.
+
+PostgresKeyValue depends on the [pg gem](https://rubygems.org/gems/pg), but
+doesn't add this as requirement, so that you can provide your own, your
+version, fork or compatible gem instead.
+
+Configuration and usage is done through dependency injection, which makes it
+easy for you to test, and to replace with mocks. The design aims to decouple as
+much as possible, allowing to integrate in the right place (and only there).
+
+A few tools are included to prepare and optimize the database. Usable in e.g.
+your migrations or a deploy script.
+
+## PostgresKeyValue is not finished!
+
+Work in Progress. Here are some evident TODOs (will be moved into github issues later)
+
+* [x] Fix glaring SQL injection holes. Use prepared statement or params to ensure clean input.
+* [ ] Determine locking and transactional behaviour: who wins on a conflict?
+* [x] Add proper index to key. Introduce some benchmark tests.
+* [ ] Allow read-only setup so that e.g. workers can read but never write.
+* [ ] Allow "connection" to be passed in from ActiveRecord (and sequel?) so that users can re-use it.
+* [x] Add tools to use in migrations or deploy scripts to setup database like we do in tests.
+* [x] Add `key?()` api to check if a key exists.
+* [x] Add `fetch()` api to provide a default and/or raise exception similar to ENV and hash.
+* [x] Add a default to initializer for the entire store. Maybe with a block, to mimic Hash.new signature?
+* [ ] Add sanitizers and protection for the JSON de- serializers e.g. storage size or formats.
+* [ ] Allow JSON de- serializers to be dependency-injected instead of using `JSON.parse` and `x.to_json`.
+* [ ] Check for more robust SQL injection protection. e.g. by force-escaping before use? See: https://stackoverflow.com/a/42281333/73673
+* [ ] Use prepared statement or params to improve performance.
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'postgres_key_value'
+```
+
+And then execute:
+
+    $ bundle install
+
+Or install it yourself as:
+
+    $ gem install postgres_key_value
+
+## Usage
+
+Steps are as follows:
+
+1. Make a connection to a postgresql database.
+2. Instantiate a PostgresKeyValue object by passing in this connection.
+3. Write to-, and read from this database.
+
+```ruby
+require 'pg'
+require 'postgres_key_value'
+
+connection = PG::Connection.open(:dbname => 'test')
+greetings = PostgresKeyValue::Store.new(connection) 
+
+greetings[:en] = "Hello World"
+greetings[:nl] = "Hallo Wereld"
+
+greetings[:en]                          #=> Hello World
+greetings['DE-de']                      #=> nil
+greetings.fetch('DE-de', 'No greeting') #=> No greeting
+greetings.key?(:nl)                     #=> true
+
+# Can be another process on another machine entirely.
+Thread.new do
+  other_greetings = PostgresKeyValue::Store.new(connection) 
+  other_greetings[:en] = "Hello Mars!"
+end.join
+
+greetings[:en]                          #=> Hello Mars!
+```
+
+## Utils
+
+Utils to create and prepare the table are provided. For example in your migrations:
+
+```ruby
+class CreateKVTableForCursors < ButtonShop::Migration
+  include PostgresKeyValue::Utils
+
+  def migrate_up
+    create_table('cursors', 'buttonshop_kv_store')
+  end
+
+  def migrate_down
+    drop_table('cursors', 'buttonshop_kv_store')
+  end
+
+  private
+
+  def connection
+    ButtonShop.config.primary_db_connection
+  end
+end
+```
+
+And in a hypthetical deployment or provisioning tool
+
+```
+class CursorsKvPreparator
+  include PostgresKeyValue::Utils
+  DB_NAME = 'buttonshop_kv_store'
+  TABLE_NAME = 'cursors'
+
+  def initialize(connection)
+    @table_name = table_name
+    @connection = connection
+  end
+
+  def prepare
+    MyInfra::Databases::CreateDatabaseCommand.new(DB_NAME)
+    create_table(TABLE_NAME, DB_NAME)
+  end
+
+  private
+
+  attr_reader :connection
+end
+
+on :staging_server do
+  CursorsKvPreparator.new(@pg_connection).prepare
+end
+```
+
+## Technical details
+
+Keys can only be strings or symbols. So be sure to convert your object to a 
+string explicitely before using.
+
+```ruby
+greetings[nil]  #=> PostgresKeyValue::InvalidKey
+greetings[42]   #=> PostgresKeyValue::InvalidKey
+greetings['']   #=> nil
+greetings['42'] #=> nil
+
+```
+
+TODO: write about
+
+* transactions
+* indexes
+* connection pools
+* read/write copies
+
+Database is configured to store key/value in two columns: key is primary key,
+value of type json. Primary is of type string, so PG limitation on keys and string
+storage apply.
+
+PostgresKeyValue deliberately tries not to be fully compatible with Hash. But it 
+does offer a similar interface. Mainly because such an opaque abstraction is leaky:
+
+A table with KV storages can, by design, grow very large, whereas a hash is
+memory bound. so features like iterators `store.each {|k,v| ... }` or
+`store.to_a` require the underlying limits to leak through. We'd then need
+logic, config, etc to handle when the database becomes too big for memory to hold.
+
+We allow keys only to be strings, and not "anything" as hash does. The database
+stores keys as strings, so if we'd allow "anything" as key, the marshalling or
+serializing would not only become complex, it puts a performance hit on all
+usage: so the ones using it with strings as keys would become slower too. 
+
+The values are serialized using JSON. This is lossy. This is by-design, but for
+security reasons. Marshalling code `object.marshall` retains the entire state,
+including methods, or callbacks and allows the provider of data to even
+monkeypatch your ruby codebase. We chose for JSON, as that is simplest, and
+therefore secured from these attacks (unless JSON.parse is vulnarable, which is
+not unthinkable).
+
+Many methods on Hash don't make a lot of sense either. E.g. most methods that
+operate on the entire hash, like `transform_keys!` or `compact` have little use
+in a pure KV lookup system. When in need of such operations, you probably need
+an actual database-table (which, not by coincidence, the `connection` already offers!)
+
+Another reason for not wanting to have feature-parity with Hash, is that it
+would grow this gem far beyond "simple", without there being a clear need for
+all the added features. Hash is really large! Rather, if there are features you need, raise an issue
+(or write a patch) so we can determine if it fits the scope and is worth the
+extra code.
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake test` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at
+https://github.com/berkes/postgres_key_value. This project is intended to be a
+safe, welcoming space for collaboration, and contributors are expected to
+adhere to the [code of conduct](https://github.com/berkes/postgres_key_value/blob/master/CODE_OF_CONDUCT.md).
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+
+## Code of Conduct
+
+Everyone interacting in the PostgresKeyValue project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/berkes/postgres_key_value/blob/master/CODE_OF_CONDUCT.md).

data/Rakefile

@@ -0,0 +1,21 @@
+# frozen_string_literal: true
+
+require 'bundler/gem_tasks'
+require 'rake/testtask'
+
+Rake::TestTask.new(:test) do |t|
+  t.libs << 'test'
+  t.libs << 'lib'
+  t.test_files = FileList['test/**/*_test.rb']
+end
+
+Rake::TestTask.new(:benchmark) do |t|
+  t.libs << 'benchmark'
+  t.libs << 'lib'
+  t.test_files = FileList['benchmark/**/*_benchmark.rb']
+end
+require 'rubocop/rake_task'
+
+RuboCop::RakeTask.new
+
+task default: %i[test rubocop]

data/bin/console

@@ -0,0 +1,15 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+require 'bundler/setup'
+require 'postgres_key_value'
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don't forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+require 'irb'
+IRB.start(__FILE__)

data/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/lib/postgres_key_value/errors.rb

@@ -0,0 +1,7 @@
+# frozen_string_literal: true
+
+module PostgresKeyValue
+  class Error < StandardError; end
+  class KeyLimitExceeded < StandardError; end
+  class InvalidKey < StandardError; end
+end

data/lib/postgres_key_value/store.rb

@@ -0,0 +1,80 @@
+# frozen_string_literal: true
+
+module PostgresKeyValue
+  ##
+  # Interact with the Key Value Store
+  class Store
+    def initialize(connection, table, default = nil, &block)
+      @connection = connection
+      @table = table
+
+      @default = default
+      @block = block_given? ? block : nil
+      raise ArgumentError, 'cannot provide both default value and default block' if @default && @block
+    end
+
+    def []=(key, value)
+      assert_correct_key(key)
+      connection.exec_params(upsert_q, [key, value.to_json])
+    rescue PG::ProgramLimitExceeded
+      raise KeyLimitExceeded
+    end
+
+    def [](key)
+      assert_correct_key(key)
+      res = connection.exec_params(read_q, [key])
+      return instance_default(key) if res.num_tuples.zero?
+
+      val = res.getvalue(0, 0)
+      JSON.parse(val)
+    end
+
+    def key?(key)
+      assert_correct_key(key)
+      connection.exec_params(exists_q, [key]).num_tuples.positive?
+    end
+
+    def fetch(key, default = nil)
+      assert_correct_key(key)
+      res = connection.exec_params(read_q, [key])
+
+      if res.num_tuples.zero?
+        return default if default
+        fail KeyError, "key not found: \"#{key}\""
+      end
+
+      val = res.getvalue(0, 0)
+      JSON.parse(val)
+    end
+
+    private
+
+    def instance_default(key)
+      if @block
+        @block.call(key)
+      else
+        @default
+      end
+    end
+
+    def assert_correct_key(key)
+      return true if key.is_a?(String) || key.is_a?(Symbol)
+
+      raise InvalidKey
+    end
+
+    def upsert_q
+      "INSERT INTO #{table} (key, value) VALUES($1::text, $2::json) ON CONFLICT (key) DO UPDATE SET value = $2::json"
+    end
+
+    def read_q
+      "SELECT value FROM #{table} WHERE key = $1::text"
+    end
+
+    def exists_q
+      "SELECT 1 FROM #{table} WHERE key = $1::text LIMIT 1"
+    end
+
+    attr_reader :connection, :table
+  end
+end

data/lib/postgres_key_value/utils.rb

@@ -0,0 +1,24 @@
+# frozen_string_literal: true
+
+module PostgresKeyValue
+  ##
+  # Utilities to generate the tables, indexes and databases for use with this gem
+  module Utils
+    def create_table(table_name)
+      maintainance_connection.exec("CREATE TABLE #{table_name} (key VARCHAR PRIMARY KEY, value json)")
+    end
+
+    def drop_table(table_name)
+      maintainance_connection.exec("DROP TABLE #{table_name}")
+    end
+
+    protected
+
+    def maintainance_connection
+      raise(
+        NotImplementedError,
+        'including class must implement maintainance_connection with CREATE/DROP table permissions'
+      )
+    end
+  end
+end

data/lib/postgres_key_value/version.rb

@@ -0,0 +1,5 @@
+# frozen_string_literal: true
+
+module PostgresKeyValue
+  VERSION = '0.2.0'
+end

data/lib/postgres_key_value.rb

@@ -0,0 +1,10 @@
+# frozen_string_literal: true
+
+require_relative 'postgres_key_value/version'
+require_relative 'postgres_key_value/errors'
+require_relative 'postgres_key_value/store'
+
+##
+# Namespace for the gem.
+module PostgresKeyValue
+end

data/postgres_key_value.gemspec

@@ -0,0 +1,29 @@
+# frozen_string_literal: true
+
+require_relative 'lib/postgres_key_value/version'
+
+Gem::Specification.new do |spec|
+  spec.name          = 'postgres_key_value'
+  spec.version       = PostgresKeyValue::VERSION
+  spec.authors       = ["Bèr Kessels\n"]
+  spec.email         = ['ber@berk.es']
+
+  spec.summary       = 'Key-Value storage for Posgresql'
+  spec.description   = "Performant and simple key-value storage in Posgresql. \
+                        With a Hash-like interface. Only dependency is pg gem"
+  spec.homepage      = 'https://github.com/berkes/postgres_key_value'
+  spec.license       = 'MIT'
+  spec.required_ruby_version = Gem::Requirement.new('>= 2.4.0')
+
+  spec.metadata['allowed_push_host'] = 'https://rubygems.org/'
+
+  spec.metadata['homepage_uri'] = spec.homepage
+  spec.metadata['source_code_uri'] = 'https://github.com/berkes/postgres_key_value'
+
+  spec.files = Dir.chdir(File.expand_path(__dir__)) do
+    `git ls-files -z`.split("\x0").reject { |f| f.match(%r{\A(?:test|spec|features|benchmark)/}) }
+  end
+  spec.bindir        = 'exe'
+  spec.executables   = spec.files.grep(%r{\Aexe/}) { |f| File.basename(f) }
+  spec.require_paths = ['lib']
+end

metadata

@@ -0,0 +1,87 @@
+--- !ruby/object:Gem::Specification
+name: postgres_key_value
+version: !ruby/object:Gem::Version
+  version: 0.2.0
+platform: ruby
+authors:
+- 'Bèr Kessels
+
+  '
+autorequire: 
+bindir: exe
+cert_chain:
+- |
+  -----BEGIN CERTIFICATE-----
+  MIIDHDCCAgSgAwIBAgIBATANBgkqhkiG9w0BAQsFADAcMRowGAYDVQQDDBFiZXIv
+  REM9YmVyay9EQz1lczAeFw0yMjAzMTUxMTI5MzRaFw0yMzAzMTUxMTI5MzRaMBwx
+  GjAYBgNVBAMMEWJlci9EQz1iZXJrL0RDPWVzMIIBIjANBgkqhkiG9w0BAQEFAAOC
+  AQ8AMIIBCgKCAQEAsXQSBxd/3i1bUOMduBWCQ71XIaLTTGhYdCWe2m19iT+43SKh
+  2Eb35bTZkRnGI5gTJGo85nmdbjIJSAByUAVCEji46zf9i2wCpoSVZpFsDdsw2mAC
+  /GTGx7TVReLbDzjLw1G2z9vTO123q65vOxv8dEMjObtXhz21dlW9TdzxC9lODRoB
+  mPIguPdfQf69B1zYS6Ai/hK/oPEOj7Od18RCnlF1+Xe3ew8+R5nVZRG1H5IIU562
+  7OgPgmtmBJrTEgt1bpZvALXGl8f4HPkkEs+BxnTP5Uju1fPLtHPXLXiP7nm2Em5q
+  9xKjJwlRn8HGyesKaPMBNxTmHTBf5G5VHpuv8wIDAQABo2kwZzAJBgNVHRMEAjAA
+  MAsGA1UdDwQEAwIEsDAdBgNVHQ4EFgQU7UHvUt2G+emOGVsmsBRLOserCz0wFgYD
+  VR0RBA8wDYELYmVyQGJlcmsuZXMwFgYDVR0SBA8wDYELYmVyQGJlcmsuZXMwDQYJ
+  KoZIhvcNAQELBQADggEBAErrSFPXfRC8VF8wPIxKAOhah/pqryBLqzYW4+E3LpN0
+  AzcDoHT9Iq5vXMZNzuEE/IhtnUvPf/MjplH0o17d+qbAGYbR8nSWKd4PSvm9an17
+  wQbn4MnJX0IyVVsKmqHV6M1ZRHqZ5yFz05OW9lboOT2Tn2wWmy3ygU/iue1GfVpg
+  hyrjlnG4hkaQxTN+nzpO+OpBLshD+hexjeAQb5WEme1lESO8xXN2182QVmdFwRv1
+  zmmrAjmKS0AWvpoxyX6PK0q5Z0PbMELNaTXQtsgXBhUITwSXyyrWQzMHZoco1LhH
+  0Xd8MPh6al9zwQaMQchpSYsHoOX8zAJW2udyDdyylJo=
+  -----END CERTIFICATE-----
+date: 2022-03-15 00:00:00.000000000 Z
+dependencies: []
+description: Performant and simple key-value storage in Posgresql.                         With
+  a Hash-like interface. Only dependency is pg gem
+email:
+- ber@berk.es
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".env.template"
+- ".github/workflows/main.yml"
+- ".gitignore"
+- ".rubocop.yml"
+- CODE_OF_CONDUCT.md
+- Gemfile
+- Gemfile.lock
+- LICENSE.txt
+- README.md
+- Rakefile
+- bin/console
+- bin/setup
+- lib/postgres_key_value.rb
+- lib/postgres_key_value/errors.rb
+- lib/postgres_key_value/store.rb
+- lib/postgres_key_value/utils.rb
+- lib/postgres_key_value/version.rb
+- postgres_key_value.gemspec
+homepage: https://github.com/berkes/postgres_key_value
+licenses:
+- MIT
+metadata:
+  allowed_push_host: https://rubygems.org/
+  homepage_uri: https://github.com/berkes/postgres_key_value
+  source_code_uri: https://github.com/berkes/postgres_key_value
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: 2.4.0
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 3.2.3
+signing_key: 
+specification_version: 4
+summary: Key-Value storage for Posgresql
+test_files: []