oplogjam 0.1.0 → 0.1.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.
- checksums.yaml +4 -4
- data/README.md +4 -4
- data/lib/oplogjam/delete.rb +1 -1
- data/lib/oplogjam/insert.rb +1 -1
- data/lib/oplogjam/operators/field_assignment.rb +1 -1
- data/lib/oplogjam/operators/index_assignment.rb +1 -1
- data/lib/oplogjam/update.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 7a88754d088c1ec7dd593b3a78203dab65dbbd68
|
4
|
+
data.tar.gz: a1113e56fe3d5984f59f38dcbf82f783194c4443
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 942b168ee61ef9d2b55c6f313436efd9aaf495a640abb4f1a7d1ddd6f52fe81e40355a3fd618bbe8b80735cc0b5b2811b64d3993a29a9fd9fd5dff5dfca88f4b
|
7
|
+
data.tar.gz: 54b56e0d1faad407489259cc84fe9c566ac014a0f71451f29c411989a04dcbd64a61cbc74e26d24e61fe402e52c166b2b773a55f02924a350a42f58ecf21c8a4
|
data/README.md
CHANGED
@@ -1,6 +1,6 @@
|
|
1
1
|
# Oplogjam [](https://travis-ci.org/mudge/oplogjam)
|
2
2
|
|
3
|
-
**Current version:** 0.1.
|
3
|
+
**Current version:** 0.1.1
|
4
4
|
**Supported Ruby versions:** 2.0, 2.1, 2.2
|
5
5
|
**Supported MongoDB versions:** 2.4, 2.6, 3.0, 3.2, 3.4
|
6
6
|
**Supported PostgreSQL versions:** 9.5, 9.6
|
@@ -86,7 +86,7 @@ With that specific use case in mind, I wanted to explore whether a library to _s
|
|
86
86
|
|
87
87
|
## Why doesn't this project come with some sort of executable?
|
88
88
|
|
89
|
-
While the library is more opinionated about the data schema of PostgreSQL, it doesn't attempt to make any decisions about how you decide which collections you want to replicate and where they should be replicated to. Similarly, connecting to databases, logging, etc. are all left up to the user as something that can
|
89
|
+
While the library is more opinionated about the data schema of PostgreSQL, it doesn't attempt to make any decisions about how you decide which collections you want to replicate and where they should be replicated to. Similarly, connecting to databases, logging, etc. are all left up to the user as something that can differ wildly.
|
90
90
|
|
91
91
|
While in future I may add an executable, for now this is up to the user to manage.
|
92
92
|
|
@@ -229,13 +229,13 @@ Note that the `name` may be a single `String`, `Symbol` or a [Sequel qualified i
|
|
229
229
|
|
230
230
|
If the indexes already exist on the given table, the method will do nothing.
|
231
231
|
|
232
|
-
#### `Oplogjam::Schema#import(collection, name)`
|
232
|
+
#### `Oplogjam::Schema#import(collection, name[, batch_size = 100])`
|
233
233
|
|
234
234
|
```ruby
|
235
235
|
schema.import(mongo[:bar], :foo_bar)
|
236
236
|
```
|
237
237
|
|
238
|
-
|
238
|
+
Import all existing documents from a given [`Mongo::Collection`](http://api.mongodb.com/ruby/current/Mongo/Collection.html) `collection` into the PostgreSQL table with the given `name` in batches of `batch_size` (defaults to 100). Note that the `name` may be a single `String`, `Symbol` or [Sequel qualified identifier](https://github.com/jeremyevans/sequel/blob/master/doc/sql.rdoc#identifiers) if you're using PostgreSQL schema.
|
239
239
|
|
240
240
|
For performance, it's better to import existing data _before_ adding indexes to the table (hence the separate [`create_table`](#oplogjamschemacreate_tablename) and [`add_indexes`](#oplogjamschemaadd_indexesname) methods).
|
241
241
|
|
data/lib/oplogjam/delete.rb
CHANGED
data/lib/oplogjam/insert.rb
CHANGED
data/lib/oplogjam/update.rb
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: oplogjam
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.1.
|
4
|
+
version: 0.1.1
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Paul Mucur
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2017-09-
|
11
|
+
date: 2017-09-14 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: bson
|