tmx_data_update 0.3.0 → 0.3.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/README.md +3 -0
- data/lib/tmx_data_update/updater.rb +4 -1
- metadata +2 -2
data/README.md
CHANGED
|
@@ -1,5 +1,8 @@
|
|
|
1
1
|
# TMX Data Update
|
|
2
2
|
|
|
3
|
+
[](http://travis-ci.org/TMXCredit/tmx_data_update)
|
|
4
|
+
[](https://codeclimate.com/github/TMXCredit/tmx_data_update)
|
|
5
|
+
|
|
3
6
|
The problem of seed data can get annoying once your Rails app is in production.
|
|
4
7
|
Ordinarily, you would place your seeds data in `seeds.rb`. Unfortunately, once
|
|
5
8
|
your application goes live, you will likely not be in a position to reload your
|
|
@@ -8,7 +8,10 @@ module TmxDataUpdate
|
|
|
8
8
|
# The module should only implement methods relevant in the context of data
|
|
9
9
|
# updates.
|
|
10
10
|
module ActiveRecordMigrationCompatible
|
|
11
|
-
|
|
11
|
+
# @see ActiveRecord::ConnectionAdapters::DatabaseStatements#execute
|
|
12
|
+
def execute(*args, &block)
|
|
13
|
+
::ActiveRecord::Base.connection.execute(*args, &block)
|
|
14
|
+
end
|
|
12
15
|
end
|
|
13
16
|
|
|
14
17
|
# The base class for all post-release data updates
|
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: tmx_data_update
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.3.
|
|
4
|
+
version: 0.3.1
|
|
5
5
|
prerelease:
|
|
6
6
|
platform: ruby
|
|
7
7
|
authors:
|
|
@@ -9,7 +9,7 @@ authors:
|
|
|
9
9
|
autorequire:
|
|
10
10
|
bindir: bin
|
|
11
11
|
cert_chain: []
|
|
12
|
-
date: 2013-
|
|
12
|
+
date: 2013-06-18 00:00:00.000000000 Z
|
|
13
13
|
dependencies:
|
|
14
14
|
- !ruby/object:Gem::Dependency
|
|
15
15
|
name: activesupport
|