active_record_content_blob 0.1.3 → 0.1.4

checksums.yaml

@@ -1,15 +1,15 @@
 ---
 !binary "U0hBMQ==":
   metadata.gz: !binary |-
-    NzUwMzA2MjM5MDY2YTRkMWEzNzk1NjJlNjQ4YjhlN2YxYzhjNmFmNQ==
+    NDdhNzkzYWRkMTk2YmM1MjFmZTBlNzE1NTYzNzgxZDMzZjhhNTM4ZQ==
   data.tar.gz: !binary |-
-    NTdlYmZmYTU1YjAxNjgzOTk1OGM5ZGQ2NDE0Y2VmYTliYjZmN2VlOQ==
+    ZmIxY2U3MzI0MjMxNzdhNzhhNWMxODA0NTFmOTc0MDljMjA4M2FmZA==
 !binary "U0hBNTEy":
   metadata.gz: !binary |-
-    ZTNhMWNlODNmOWQyYjQ0MTdiYjdmNjFkNDNlNmE0ZDg3OGY0NTVhNGYzYzQ1
-    MzFlMWZhNTFmYmMwY2I4YWI0NjBiY2JiZTIwNWIwYTFlN2I4ZTUzMDU3ZWYx
-    NjljYzYxOWMxMjUzODY3OTUwZTE5MWQ2Y2ZmZTU1OTc4MTFiMjU=
+    MWQ5ODRmMWJkOTFkMTQ1YzEzNjRiYTk4ZGUwNTVmODM0YWQ0ZDI4ZmI0YjM3
+    NWE2Yjc2NDFhNDI0ZWMwYzdiMmE4M2E0ODcyOTY1MTVjNDJmNjAzNTBhYzg0
+    Y2NhZDljMWYzMWVhOGU2MjU2YjBiMjkyNWQ0NmNkNjc2MzhhZDg=
   data.tar.gz: !binary |-
-    MjQ5YTA1MjdhMzI4NzcxZDVjN2NjNmEwZWM1NDEwY2NlNmU5NDVhOWU4ZmY1
-    M2FkODEyYWZlMmE1Mjc3MGNhOWRhN2ZhYWQ2ZTliNzA3YzNmNDJlODgzNDQ5
-    N2FkOTBjY2E4NzBjNjIwODlkODVkZjlhYmU0OWI0OWY0ZmEyMWE=
+    ZjA5NzkxMmUyZGFiN2M3ODkwNDAwZTlmZDA1ZmJjMjkyYWM0MDYzZmRlYmU2
+    OWYxMjUxNDRhZTU2YjEwMzE0Zjc4N2JkZjFmZjFkNTVkYzY0MmQxYWE3Zjkx
+    MWM2MDU4MTY4ZTRmMGUwMjc3NzhhNjQ2ZDQ4YjlkYWM5Y2E1YWI=

data/README.md

@@ -0,0 +1,44 @@
+# ActiveRecordContentBlob
+
+A convenience gem for associating serialized BLOBs with your records, if you happen to use blobs to store data that doesn't need to be scoped.
+
+For example, when backing up Tweet data, a user may find it to have a `tweets` table containing fields such as `created_at`, so that they can query for all Tweets within a certain time period. But the other content that comes with a Tweet might be useful later, so it's convenient to stick the entire JSON representation of a Tweet into a BLOB.
+
+But because ActiveRecord::Base will `select` all columns by default, querying across a large set of `tweets` will [slow performance](http://stackoverflow.com/questions/9511476/speed-of-mysql-query-on-tables-containing-blob-depends-on-filesystem-cache).
+
+
+`ActiveRecordContentBlob` is simply a convenience gem that creates a polymorphic relationship between any other AR table.
+
+
+**Note:** This is something I'm playing around with. I don't recommend it for production at this point.
+
+## Installation
+
+    gem install active_record_content_blob
+
+
+Include it in your `Gemfile`
+
+    bundle install
+
+Run the `rake` task to modify your database
+
+    rails generate content_blob
+    rake db:migrate
+
+Sample usage:
+
+      record = MusicRecord.new
+      record.build_a_blob({'title' => "The Jackson 5"})
+      record.save
+
+      record.contents['title']
+      # => The Jackson 5 
+
+
+
+
+
+
+
+

data/VERSION

@@ -1 +1 @@
-0.1.3
+0.1.4

data/active_record_content_blob.gemspec

@@ -5,7 +5,7 @@
 
 Gem::Specification.new do |s|
   s.name = "active_record_content_blob"
-  s.version = "0.1.3"
+  s.version = "0.1.4"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Dan Nguyen"]
@@ -14,7 +14,7 @@ Gem::Specification.new do |s|
   s.email = "dansonguyen@gmail.com"
   s.extra_rdoc_files = [
     "LICENSE.txt",
-    "README.rdoc"
+    "README.md"
   ]
   s.files = [
     ".document",
@@ -22,7 +22,7 @@ Gem::Specification.new do |s|
     "Gemfile",
     "Gemfile.lock",
     "LICENSE.txt",
-    "README.rdoc",
+    "README.md",
     "Rakefile",
     "VERSION",
     "active_record_content_blob.gemspec",

data/lib/content_blob.rb

@@ -2,7 +2,7 @@ require 'active_record'
 require 'active_support'
 class ContentBlob < ActiveRecord::Base 
 
-
+   attr_accessible :contents
    serialize :contents
 
    validates_uniqueness_of :blobable_id, scope: :blobable_type

data/spec/unit/blobable_spec.rb

@@ -9,8 +9,6 @@ class BadRecord < ActiveRecord::Base; end
 describe "Blobable" do
   before(:each) do 
     DatabaseCleaner.clean
-    MusicRecord.delete_all
-    ContentBlob.delete_all
   end
 
   it 'should raise an error if a class has :contents as an actual field' do 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: active_record_content_blob
 version: !ruby/object:Gem::Version
-  version: 0.1.3
+  version: 0.1.4
 platform: ruby
 authors:
 - Dan Nguyen
@@ -128,14 +128,14 @@ executables: []
 extensions: []
 extra_rdoc_files:
 - LICENSE.txt
-- README.rdoc
+- README.md
 files:
 - .document
 - .rspec
 - Gemfile
 - Gemfile.lock
 - LICENSE.txt
-- README.rdoc
+- README.md
 - Rakefile
 - VERSION
 - active_record_content_blob.gemspec

data/README.rdoc

@@ -1,19 +0,0 @@
-= active_record_content_blob
-
-Description goes here.
-
-== Contributing to active_record_content_blob
- 
-* Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet.
-* Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it.
-* Fork the project.
-* Start a feature/bugfix branch.
-* Commit and push until you are happy with your contribution.
-* Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
-* Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.
-
-== Copyright
-
-Copyright (c) 2013 Dan Nguyen. See LICENSE.txt for
-further details.
-