flounder 0.9.8 → 0.9.9

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 0b671fc956d5fcd73817cdc07ec5e9dbd5b03751
-  data.tar.gz: 1a6cf5f585030c036c5bd57abf4450d25103e529
+  metadata.gz: 940cc41b4684232c361a86fd4959dfef55b870b1
+  data.tar.gz: 1a06c9aad7acfb5a10a27338a63a384aaaa1b159
 SHA512:
-  metadata.gz: 7803a9083fa04f1f3c0cef3ac9a781f699c55194676e4f362f610a38ff663f3893d07dc1de5da525eaafada13935bbc34c44f56e40218962096790c96e776d69
-  data.tar.gz: 409cd4865b56744ae81129d6cc3eee861fb050c37bcda5943acad18885dca809e1d6c5fb779ce2bc220d33ebcd3171b1e8c84bf81367d92bbf6db827c82221f4
+  metadata.gz: b9172f01e03b4df6ae1e4ee05f88440a4adffd478d8908458790e6cfed7db595b42c3b2af62fae8d41456dbb2761a63f9238503f0d5e9ca56fa2b5d8c9b5de1e
+  data.tar.gz: 0df7ef74347458c652bf98a4f949153e25e97b8a8aed5e7372ac19d5527e32c6de5bf6e43feac782d3b74afc12384240612bd552b5eb14dff6cfb79dc0516d32

data/Gemfile.lock

@@ -0,0 +1,33 @@
+PATH
+  remote: .
+  specs:
+    flounder (0.9.8)
+      arel (~> 5, > 5.0.1)
+      connection_pool (~> 2)
+      hashie (~> 3, >= 3.2)
+      pg (~> 0.17)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    ae (1.8.2)
+      ansi
+    ansi (1.4.3)
+    arel (5.0.1.20140414130214)
+    brass (1.2.1)
+    connection_pool (2.0.0)
+    facets (2.9.3)
+    hashie (3.2.0)
+    pg (0.17.1)
+    qed (2.9.1)
+      ansi
+      brass
+      facets (>= 2.8)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  ae
+  flounder!
+  qed

data/HISTORY

@@ -11,4 +11,5 @@
  + nested transactions
  + subquery support
  + localized where as in where(entity, :field => value)
- + db.where(entity, hash) form, where all symbols are looked up in entity. 
+ + db.where(entity, hash) form, where all symbols are looked up in entity. 
+ + db.entity.join(:other_entity) is now allowed

data/flounder.gemspec

@@ -2,7 +2,7 @@
 
 Gem::Specification.new do |s|
   s.name     = "flounder"
-  s.version  = '0.9.8'
+  s.version  = '0.9.9'
   s.summary  = "Flounder is a way to write SQL simply in Ruby. It deals with everything BUT object relational mapping. "
   s.email    = "kaspar.schiess@technologyastronauts.ch"
   s.homepage = "https://bitbucket.org/technologyastronauts/oss_flounder"

data/lib/flounder/query/select.rb

@@ -31,6 +31,8 @@ module Flounder::Query
     attr_reader :projection_prefixes
 
     def _join join_node, entity
+      entity = domain[entity] if entity.kind_of?(Symbol)
+
       @last_join = entity
 
       table = entity.table

data/qed/index.md

@@ -82,6 +82,14 @@ Here are some non-crazy joins that also work.
     assert generates_sql(%Q(SELECT [fields] FROM "users" LEFT OUTER JOIN "posts" ON "users"."id" = "posts"."user_id"))
 ~~~
 
+You might want to drop the calls to domain. 
+
+~~~ruby 
+  domain[:users].join(:posts).on(:id => :user_id).
+    assert generates_sql(
+      %Q(SELECT [fields] FROM "users" INNER JOIN "posts" ON "users"."id" = "posts"."user_id"))
+~~~
+
 Joining presents an interesting dilemma. There are two ways of joining things together, given three tables. The sequence A.B.C might mean to join A to B and C; it might also be interpreted to mean to join A to B and B to C. Here's how we solve this. 
 
 ~~~ruby

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: flounder
 version: !ruby/object:Gem::Version
-  version: 0.9.8
+  version: 0.9.9
 platform: ruby
 authors:
 - Kaspar Schiess
@@ -88,6 +88,7 @@ extensions: []
 extra_rdoc_files: []
 files:
 - Gemfile
+- Gemfile.lock
 - HACKING
 - HISTORY
 - LICENSE