multitenant-mysql 1.0.0 → 1.0.1

data/README.rdoc

@@ -7,6 +7,7 @@ The idea is taken from http://blog.empowercampaigns.com/post/1044240481/multi-te
 The advantages of such approach:
 - no default scopes
 - only one db
+- no Threads
 - the biggest advantage is that responsebility about the data is moved to the db layer. It means the customer shouldn't be warry about developer's mistake before very critical demo and the logic of the app is much simplier.
 
 == Code Status

data/lib/multitenant-mysql/conf_file.rb

@@ -11,7 +11,7 @@ module Multitenant
       end
 
       def self.full_path
-        path << '.rb'
+        "#{path}.rb"
       end
 
       def self.default_path

data/lib/multitenant-mysql/version.rb

@@ -1,5 +1,5 @@
 module Multitenant
   module Mysql
-    VERSION = "1.0.0"
+    VERSION = "1.0.1"
   end
 end

data/spec/conf_file_spec.rb

@@ -24,6 +24,13 @@ describe Multitenant::Mysql::ConfFile do
       subject.path = '/conf/file'
       expect(subject.full_path).to eql('/conf/file.rb')
     end
+
+    it 'should return correct path no metter how many times we call it' do
+      subject.path = '/conf/file'
+      2.times do
+        expect(subject.full_path).to eql('/conf/file.rb')
+      end
+    end
   end
 
   context '.default_path' do

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: multitenant-mysql
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.0.1
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-02-17 00:00:00.000000000 Z
+date: 2013-02-18 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rspec
@@ -83,7 +83,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.21
+rubygems_version: 1.8.24
 signing_key: 
 specification_version: 3
 summary: Add multi-tenancy to Rails application using MySql views