sequel_pg_ltree 0.1.7 → 0.1.8

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7ec4a0f98416a8125869c029d0161a5ae0479cf05a9dda405667e9806c5f0363
-  data.tar.gz: a54a34f6ac63a1e1f1e8a209401582998bf2de296b175f46ff77e58cc7e501c7
+  metadata.gz: f36b537ec4b27058e26125def8bacc8692ef76707041ec8f27f87312bfd81208
+  data.tar.gz: c59b6efe87adcf4aefb92c80e9916c2bb80d98410bc1519ede0249c3e402767e
 SHA512:
-  metadata.gz: 030d4041ffbb252dafc0decd672c23bc1dbc6046dd7f5557d3faf708c6f03d478e83783ca43414cdcaf5fb5641326d007a7f8c972aff6800d3ffebe53a4dc67a
-  data.tar.gz: 61590a5c2b7491984b01384eb11e902d2ceea730c69d8d55a90b2b71b1e19222043a6baafce034beb8ab88f0f58bdd5a7dc0220c1665d8c5fbd092c9346e9719
+  metadata.gz: 35592042137f578b59d32f9117f18ed8821470b80c58be18d6dc4b4f41206c721a030efc0c111be17e820667d878f6a2ef661a2f22e36f8bd9629294fb411c42
+  data.tar.gz: 85f44df34d3bd42fdac97c10ffb93b28dbc18293682b83528466d737c560e92c1230ecd89c7b95a1de9be05ecf42579512c4ecb38860cfd00729b772b6037c12

data/Gemfile

@@ -1,6 +1,4 @@
 source "https://rubygems.org"
 
-#git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
-
 # Specify your gem's dependencies in sequel_pg_ltree.gemspec
 gemspec

data/LICENSE.txt

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2019 TODO: Write your name
+Copyright (c) 2019 b10wf15h
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

data/README.md

@@ -1,8 +1,7 @@
 # SequelPgLtree
 
-Welcome to your new gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file `lib/sequel_pg_ltree`. To experiment with that code, run `bin/console` for an interactive prompt.
-
-TODO: Delete this and the text above, and describe your gem
+## notice
+Sequel ORM postgresql ltree helper inspired by https://github.com/sjke/pg_ltree
 
 ## Installation
 
@@ -22,22 +21,30 @@ Or install it yourself as:
 
 ## Usage
 
-TODO: Write usage instructions here
-
-## Development
-
-After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` 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 tags, 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/[USERNAME]/sequel_pg_ltree. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
+```sql
+ id | path
+----+-------
+  1 | A
+  2 | A.B
+  3 | A.C
+  4 | A.C.D
+  5 | A.C.E
+  6 | A.C.F
+  7 | A.B.G
+```
 
-## License
+```ruby
+class Tree < Sequel::Model(:tree)
+  plugin :pg_ltree, :column => :path
+end
 
-The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+Tree.find(id: 2).root.path # => A
+Tree.find(id: 2).parent.path # => A
+Tree.where(id: 1).first.children.each do |c|
+  c[:path]
+end # => A.B  A.C
 
-## Code of Conduct
+```
 
-Everyone interacting in the SequelPgLtree project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/sequel_pg_ltree/blob/master/CODE_OF_CONDUCT.md).
+## TODO
+tests should be added

data/lib/sequel/plugins/pg_ltree/version.rb

@@ -2,6 +2,6 @@ module Sequel
   # The Sequel::PgLtree model plugin
   module PgLtree
     # The Gem's version.
-    VERSION = "0.1.7".freeze
+    VERSION = "0.1.8".freeze
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: sequel_pg_ltree
 version: !ruby/object:Gem::Version
-  version: 0.1.7
+  version: 0.1.8
 platform: ruby
 authors:
 - Igor Milisav
@@ -95,7 +95,6 @@ extra_rdoc_files: []
 files:
 - ".gitignore"
 - ".travis.yml"
-- CODE_OF_CONDUCT.md
 - Gemfile
 - LICENSE.txt
 - README.md

data/CODE_OF_CONDUCT.md

@@ -1,74 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
-advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers 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, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at TODO: Write your email address. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/