chartio-rails 0.0.1 → 0.0.2
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +12 -0
- data/lib/chartio/version.rb +1 -1
- metadata +2 -4
- data/bin/chartio-rails +0 -22
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: f8bf60737d204e349cc5001ba0e255ec27d7b993
|
4
|
+
data.tar.gz: 603632bf726ca70cf92f8106e45e1811f338c6ac
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 458f5d6c73f479580d425bbf9e26f33cd736961883ea5224c6f62b67c6ae8c3727a47c4db9448d1ebdbf3c31ca4e37a274cd68642bde2f04b7f5ff0db9176baa
|
7
|
+
data.tar.gz: c057596eecb21ec98787578b8621ec0bed3f6dd3536bb9479e55130a4978c74ccb7731df3ddc570b840b02675196df8ea5e875bcdf43fe73c6b67f73e837879e
|
data/README.md
CHANGED
@@ -2,6 +2,18 @@
|
|
2
2
|
|
3
3
|
As a Rails user you're probably familiar with the fact that Rails doesn't not create foreign keys in the database. Since ActiveRecord migrations don't cover this, it makes it very hard to work with Chartio because the metadata around how tables should be joined together only lives at the application layer. Using this gem, you will be able to output the metadata around the relationships in your Rails project and, working with your Chartio Customer Success Engineer, can get the relationships you need for your database.
|
4
4
|
|
5
|
+
## Supported Version
|
6
|
+
|
7
|
+
### Ruby
|
8
|
+
|
9
|
+
* 1.9.3
|
10
|
+
* 2.0.0
|
11
|
+
* 2.1.0
|
12
|
+
|
13
|
+
### ActiveRecord
|
14
|
+
|
15
|
+
* >= 3.0.0
|
16
|
+
|
5
17
|
## Installation
|
6
18
|
|
7
19
|
Add this line to your application's Gemfile:
|
data/lib/chartio/version.rb
CHANGED
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: chartio-rails
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.0.
|
4
|
+
version: 0.0.2
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Rimas Silkaitis
|
@@ -111,8 +111,7 @@ dependencies:
|
|
111
111
|
description: Helper functions for getting your Rails database hooked up to Chartio
|
112
112
|
email:
|
113
113
|
- rimas@chartio.com
|
114
|
-
executables:
|
115
|
-
- chartio-rails
|
114
|
+
executables: []
|
116
115
|
extensions: []
|
117
116
|
extra_rdoc_files: []
|
118
117
|
files:
|
@@ -122,7 +121,6 @@ files:
|
|
122
121
|
- LICENSE.txt
|
123
122
|
- README.md
|
124
123
|
- Rakefile
|
125
|
-
- bin/chartio-rails
|
126
124
|
- chartio-rails.gemspec
|
127
125
|
- gemfiles/rails3.gemfile
|
128
126
|
- gemfiles/rails31.gemfile
|
data/bin/chartio-rails
DELETED
@@ -1,22 +0,0 @@
|
|
1
|
-
#!/usr/bin/env ruby
|
2
|
-
|
3
|
-
require 'rubygems'
|
4
|
-
require 'optparse'
|
5
|
-
require 'yaml'
|
6
|
-
begin
|
7
|
-
require 'chartio-rails'
|
8
|
-
rescue LoadError
|
9
|
-
lib = File.expand_path('../../lib', __FILE__)
|
10
|
-
$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
|
11
|
-
require File.expand_path("../../lib/chartio-rails", __FILE__)
|
12
|
-
end
|
13
|
-
|
14
|
-
options = {}
|
15
|
-
options_parser = OptionParser.new do |opts|
|
16
|
-
opts.banner = <<-TXT
|
17
|
-
A helper function to build foreign key constraints in Chartio
|
18
|
-
|
19
|
-
Usage: relateiq_dump [options]
|
20
|
-
TXT
|
21
|
-
|
22
|
-
end
|