ez_model 1.0.1 → 1.0.2

data/README.md

@@ -1,5 +1,5 @@
 # EZModel
-Generate models and schema.rb from existing database just in one command line. If you prefer design ER diagram and export scripts to generate database schema, or if you have to work with a legacy database, this can save you insame amount of time. All you need to do is to have a database.yml configuraiton file in ~/config/. Besides creating all models it sets proper table name and primary key if tables and columns naming doesn’t follow Rails convention. It also tries to read all foreign keys data from a database.     
+Generate models and schema.rb from existing database just in one command line. If you prefer design ER diagram and export scripts to generate database schema, or if you have to work with a legacy database, this can save you insane amount of time. All you need to do is to have a database.yml configuraiton file in ~/config/. Besides creating all models it sets proper table name and primary key if tables and columns naming doesn’t follow Rails convention. It also tries to read all foreign keys data from a database.     
 
 It uses [Rmre](https://github.com/bosko/rmre "Rmre") as underlying reverse engine to generate models. I made some modifications to Rmre to support mysql2 adapter, and had those auto-generated model files placed in a subfolder inside ~/app/models/ez_models/ instead of the default ~/app/models/, so that regenerating models will not overwrite the existing ones. Over the times, db schema can ge changed, all it needs is to run the command again to regenerate models, developers can feel free to add methods to the models classes in ~/app/models/ without worrying about being overwritten.
 
@@ -39,22 +39,31 @@ checkout mysql-workbench and its forward-engineering feature for more details ab
 		socket: /var/run/mysqld/mysqld.sock
 
 ###Generate models
-	# generate model files
-	# it will take development as default db environment when environment is not specified  
+cd to rails root directory   
+
+	cd /path_to_rails_root
+
+generate model files   
+it will take development as default db environment when environment is not specified  
+   
 	ezmodel -g
-	#or
+or   
+
 	ezmodel -g -e development
 
-	# generate model files and overwrite existing ones in ~/app/models/
-	# use this command only if the model files in ~/app/models/ don't inherit EZModel::ActiveRecord 
-	# backup your models files is strongly suggested if you are not sure what it is doing
-	# use it at your own risk
+generate model files and overwrite existing ones in ~/app/models/   
+use this command only if the model files in ~/app/models/ don't inherit EZModel::ActiveRecord    
+backup your models files is strongly suggested if you are not sure what it is doing   
+use it at your own risk   
+
 	ezmodel -g -o
 
-	# see help
+see help   
+
 	ezmodel -h
 
-	# see version
+see version   
+
 	ezmodel -v
 
 ## Installation

data/ez_model.gemspec

@@ -6,24 +6,33 @@ require "rmre/version"
 
 Gem::Specification.new do |s|
 
-  # Basic info
+  # Gem info
   s.name = "ez_model"
   s.version = ::EZModel::VERSION
   s.platform = Gem::Platform::RUBY
-  s.date = "2012-04-10"
-  s.summary = "Generate model files just in one command line"
-  s.description = "Generate models and schema.rb from existing database just in one command line. If you prefer design ER diagram and export scripts to generate database schema, or if you have to work with a legacy database, this can save you insame amount of time. All you need to do is to have a database.yml configuraiton file in ~/config/. Besides creating all models it sets proper table name and primary key if tables and columns naming doesn’t follow Rails convention. It also tries to read all foreign keys data from a database."
+  s.date = "2012-04-08"
+  s.summary = "%q{Generate model files just in one command line}"
+  s.description = "%q{	Generate models and schema.rb from existing database just in one command line. If you prefer design ER diagram and export scripts to generate database schema, or if you have to work with a legacy database, this can save you insane amount of time. All you need to do is to have a database.yml configuraiton file in ~/config/. Besides creating all models it sets proper table name and primary key if tables and columns naming doesn’t follow Rails convention. It also tries to read all foreign keys data from a database.
+	It uses Rmre as underlying reverse engine to generate models. I made some modifications to Rmre to support mysql2 adapter, and had those auto-generated model files placed in a subfolder inside ~/app/models/ez_models/ instead of the default ~/app/models/, so that regenerating models will not overwrite the existing ones. Over the times, db schema can ge changed, all it needs is to run the command again to regenerate models, developers can feel free to add methods to the models classes in ~/app/models/ without worrying about being overwritten.}"
+
+  # Author info
   s.authors = ["Tianyu Huang"]
   s.email = ["tianhsky@yahoo.com"]
   s.homepage = "http://rubygems.org/gems/ez_model"
 
   # Dependencies
-  # s.required_rubygems_version = ">= 1.3.6"
+  s.required_rubygems_version = ">= 1.3.6"
+  s.add_dependency "activerecord", ">= 3.0.0"
+  s.add_dependency "erubis", "~> 2.6.6"
+  #s.add_development_dependency "rspec"
 
   # Files
   s.files = `git ls-files`.split("\n")
-  s.extra_rdoc_files = ["README.md"]
+  s.require_paths = ["lib"]
   s.executables = `git ls-files -- bin/*`.split("\n").map { |f| File.basename(f) }
+  s.extra_rdoc_files = ["README.md", "LICENSE"]
+  
+  
 
 
 end

data/lib/ez_model/version.rb

@@ -1,3 +1,3 @@
 module EZModel
-  VERSION = "1.0.1" unless defined?(::EZModel::VERSION)
+  VERSION = "1.0.2" unless defined?(::EZModel::VERSION)
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: ez_model
 version: !ruby/object:Gem::Version
-  version: 1.0.1
+  version: 1.0.2
   prerelease: 
 platform: ruby
 authors:
@@ -9,15 +9,43 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-04-10 00:00:00.000000000 Z
-dependencies: []
-description: Generate models and schema.rb from existing database just in one command
-  line. If you prefer design ER diagram and export scripts to generate database schema,
-  or if you have to work with a legacy database, this can save you insame amount of
-  time. All you need to do is to have a database.yml configuraiton file in ~/config/.
-  Besides creating all models it sets proper table name and primary key if tables
-  and columns naming doesn’t follow Rails convention. It also tries to read all foreign
-  keys data from a database.
+date: 2012-04-08 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: activerecord
+  requirement: &72362480 !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: 3.0.0
+  type: :runtime
+  prerelease: false
+  version_requirements: *72362480
+- !ruby/object:Gem::Dependency
+  name: erubis
+  requirement: &72362180 !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: 2.6.6
+  type: :runtime
+  prerelease: false
+  version_requirements: *72362180
+description: ! "%q{\tGenerate models and schema.rb from existing database just in
+  one command line. If you prefer design ER diagram and export scripts to generate
+  database schema, or if you have to work with a legacy database, this can save you
+  insane amount of time. All you need to do is to have a database.yml configuraiton
+  file in ~/config/. Besides creating all models it sets proper table name and primary
+  key if tables and columns naming doesn’t follow Rails convention. It also tries
+  to read all foreign keys data from a database.\n\tIt uses Rmre as underlying reverse
+  engine to generate models. I made some modifications to Rmre to support mysql2 adapter,
+  and had those auto-generated model files placed in a subfolder inside ~/app/models/ez_models/
+  instead of the default ~/app/models/, so that regenerating models will not overwrite
+  the existing ones. Over the times, db schema can ge changed, all it needs is to
+  run the command again to regenerate models, developers can feel free to add methods
+  to the models classes in ~/app/models/ without worrying about being overwritten.}"
 email:
 - tianhsky@yahoo.com
 executables:
@@ -25,6 +53,7 @@ executables:
 extensions: []
 extra_rdoc_files:
 - README.md
+- LICENSE
 files:
 - .gitignore
 - LICENSE
@@ -59,12 +88,12 @@ required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ! '>='
     - !ruby/object:Gem::Version
-      version: '0'
+      version: 1.3.6
 requirements: []
 rubyforge_project: 
 rubygems_version: 1.8.17
 signing_key: 
 specification_version: 3
-summary: Generate model files just in one command line
+summary: ! '%q{Generate model files just in one command line}'
 test_files: []
 has_rdoc: