database_introspection 0.1.1 → 0.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 25c5d7a4888eafde894853b452a714f634b652ae
-  data.tar.gz: eb2e2cedbe5a5ff900049ba10fd485a1ed70e9bb
+  metadata.gz: c1727c6aec864d179a3b23c796659882a15ed521
+  data.tar.gz: b5e58598eef2358c11bd5c7629c6686c3537cada
 SHA512:
-  metadata.gz: 76cee6c4b5202dceb394f5efd85f67928d173b73ab52aa7d6bfd2eb2be6c6adb6fb131cd822f9655b977efddc2d303ea8ebe55c42648db9921a29015b7c5086b
-  data.tar.gz: 69824f5c5e775c980fe1081f48c83a02c3f88a4ca812c5643ea9ba25221f5eee1152e606a350816316607775b2ff1d908c885b3ab3c7710a6bd14be845dee8cd
+  metadata.gz: e1762338b41cd573f2ccedd5df814a43ed12bb6c1e8d295a83059886e3403bde0012731a5c898b1e95a6ef0985442dfaa0074ce85dce915166e794f405637beb
+  data.tar.gz: e0c74af9319c4033d337e1fb1c26b63829bb11b53b90b8eea158ea5cb0fba433f389c31c990f77c5166afc44ad73d0d972115e7230b06e699076fe7ff3951084

data/README.md

@@ -1,9 +1,18 @@
 # Database Introspection
 
-[This gem][gemref] will introspect the database and create __dynamically__ ActiveRecord::Base descendants that can be used by your application, including some Rails associations helper methods.
+[This gem][gemref] will introspect the database and create __dynamically__ ActiveRecord::Base descendants that can be
+used by your application, including some Rails associations helper methods.
 
-It is intended to be primarily used within rails applications but nothing prevents you to use standalone, provided the fact you are already connected to a database.
-This gem does a bit the reverse action of what you do with Rails generator, when you want to generate the database from you migrations.
+It is intended to be primarily used within rails applications but nothing prevents you to use standalone, provided
+the fact you are already connected to a database.
+This gem does a bit the reverse action of what you do with Rails generator, when you want to generate the database from
+you migrations.
+
+Basically, it will infer the database and create ActiveRecord::Base descendants to handle tables already defined in the database.
+
+The cool point is that it will as well guess from column names in the tables the relations between tables and dynamically
+create the associations in the generated classes and thus all helper methods (for belongs_to, has_many and even has_many
+:through).
 
 
 ## Installation

data/lib/database_introspection/dynamic_model/relations_analyser.rb

@@ -102,8 +102,8 @@ class DynamicModel::RelationsAnalyser
 
   def analyses_has_many_through_association(model, associations)
     # As there are multiple belongs_to in this class, all combinations
-    # should lead to a has_many_through
-    # Waouh, Ruby rocks !!
+    # should lead to a has_many :through
+    # Wow, Ruby rocks !!
     associations.combination(2).each do |left, right|
       @alterations[left[:class]][:has_many_through] ||= []
       @alterations[right[:class]][:has_many_through] ||= []
@@ -145,26 +145,33 @@ class DynamicModel::RelationsAnalyser
 
 
   def add_belongs_to_behaviour(model, description)
-    field_name = description[:class].list_name.singularize
-    model.belongs_to field_name, :foreign_key => description[:key], :class_name => description[:class].name
-    puts " - belongs_to :#{field_name}, :foreign_key => #{description[:key]}, :class_name => #{description[:class].name}"
+    field_name = description[:class].list_name.singularize.to_sym
+    options = {foreign_key: description[:key], class_name: description[:class].name}
+    model.belongs_to field_name, options
+    puts " - belongs_to :#{field_name}, #{options.inspect}"
   end
 
   def add_has_many_behaviour(model, description)
-    field_name = description[:class].list_name
-    model.has_many field_name, :class_name => description[:class].name
-    puts " - has_many :#{field_name}, :class_name => #{description[:class].name}"
+    field_name = description[:class].list_name.to_sym
+    options = {class_name: description[:class].name}
+    model.has_many field_name, options
+    puts " - has_many :#{field_name}, #{options.inspect}"
   end
 
+  # TODO: maybe check the intermediate class and depending upon the fact it contains a primary key, if only 2 fields
+  #       exist. It may be a habtm instead of has_many :through...
   def add_has_many_through_behaviour(model, description)
-    puts " - has_many #{description[:class]} through #{description[:middle_class]}" 
+    field_name = description[:class].list_name.to_sym
+    options = {through: description[:middle_class].list_name.to_sym, source: description[:class].list_name.singularize}
+    model.has_many field_name, options
+    puts " - has_many :#{field_name}, #{options.inspect}"
   end
 
-
   def add_has_one_behaviour(model, description)
-    field_name = description[:class].list_name.singularize
-    model.has_one field_name, :class_name => description[:class].name
-    puts " - has_one :#{field_name}, :class_name => #{description[:class].name}"
+    field_name = description[:class].list_name.singularize.to_sym
+    options = {class_name: description[:class].name}
+    model.has_one field_name, options
+    puts " - has_one :#{field_name}, #{options.inspect}"
   end
 
 end

data/lib/database_introspection/version.rb

@@ -1,3 +1,3 @@
 module DatabaseIntrospection
-  VERSION = "0.1.1"
+  VERSION = "0.2.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: database_introspection
 version: !ruby/object:Gem::Version
-  version: 0.1.1
+  version: 0.2.0
 platform: ruby
 authors:
 - L.Briais
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-05-25 00:00:00.000000000 Z
+date: 2013-05-26 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler