Pete
2013-Feb-22 16:37 UTC
Model generator: Invoke active_record only 1x for mulitiple models?
Currently (3.2.12), Rails needs 1 separate command per model/migration
to be generated. Each such "rails g ..." command invokes active_record
once.
When a project needs to generate a larger number of models/migrations,
this process can take up lots of time.
So, this...
rails g model_a name:string [...]
rails g model_b name:string [...]
rails g model_c name:string [...]
...etc...
invoke active_record
create db/migrate/201302...
create app/models/model_a.rb
[...]
invoke active_record
create db/migrate/201302...
create app/models/model_b.rb
[...]
invoke active_record
create db/migrate/201302...
create app/models/model_c.rb
[...]
...etc...
...should become something (speedier) like this:
rails g model_a name:string [...], model_b name:string [...],
model_c name:string [...] ...etc...
invoke active_record
create db/migrate/201302...
create app/models/model_a.rb
[...]
create db/migrate/201302...
create app/models/model_b.rb
[...]
create db/migrate/201302...
create app/models/model_c.rb
[...]
...etc...
--
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rubyonrails-core+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Borna Novak
2013-Feb-23 19:48 UTC
Re: Model generator: Invoke active_record only 1x for mulitiple models?
Pete, this project saved a couple of years of my life already: https://github.com/burke/zeus Basically, it runs rake jobs, generators, destroyers, tests... in under a second by preloading the various environments and then just forking an appropriate existing process when a command is triggered, real life-saver Borna On Friday, February 22, 2013 5:37:36 PM UTC+1, Pete wrote:> > Currently (3.2.12), Rails needs 1 separate command per model/migration > to be generated. Each such "rails g ..." command invokes active_record once. > > > When a project needs to generate a larger number of models/migrations, > this process can take up lots of time. > > So, this... > > rails g model_a name:string [...] > rails g model_b name:string [...] > rails g model_c name:string [...] > ...etc... > > invoke active_record > create db/migrate/201302... > create app/models/model_a.rb > [...] > invoke active_record > create db/migrate/201302... > create app/models/model_b.rb > [...] > invoke active_record > create db/migrate/201302... > create app/models/model_c.rb > [...] > ...etc... > > ...should become something (speedier) like this: > > rails g model_a name:string [...], model_b name:string [...], > model_c name:string [...] ...etc... > > invoke active_record > create db/migrate/201302... > create app/models/model_a.rb > [...] > create db/migrate/201302... > create app/models/model_b.rb > [...] > create db/migrate/201302... > create app/models/model_c.rb > [...] > ...etc... >-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscribe@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Carlos Antonio da Silva
2013-Feb-23 22:30 UTC
Re: Re: Model generator: Invoke active_record only 1x for mulitiple models?
Yes, zeus is a nice one to speed up development lifecycle. There''s also spring <http://github.com/jonleighton/spring>, a new tool from jonleighton that''s under test and is likely to be the default integration with Rails as part of the development process, I recommend you guys to take a look. Pete, I think the path that zeus and spring are taking is the way to go, since it does not help only with model generators, but speeds up generators, console, tests, and everything else related to our development workflow. On Sat, Feb 23, 2013 at 4:48 PM, Borna Novak <dosadnizub@gmail.com> wrote:> Pete, > > this project saved a couple of years of my life already: > https://github.com/burke/zeus > > Basically, it runs rake jobs, generators, destroyers, tests... in under a > second by preloading the various environments and then just forking an > appropriate existing process when a command is triggered, real life-saver > > > Borna > > > On Friday, February 22, 2013 5:37:36 PM UTC+1, Pete wrote: >> >> Currently (3.2.12), Rails needs 1 separate command per model/migration >> to be generated. Each such "**rails g ..." command invokes **active_record once. >> >> >> When a project needs to generate a larger number of models/migrations, >> this process can take up lots **of time. >> >> So, this... >> >> rails g model_a name:**string [...] >> rails g model_b name:**string [...] >> rails g model_c name:**string [...] >> ...etc... >> >> invoke active_record >> create db/migrate/**201302... >> create app/models/**model_a.rb >> [...] >> invoke active_record >> create db/migrate/**201302... >> create app/models/**model_b.rb >> [...] >> invoke active_record >> create db/migrate/**201302... >> create app/models/**model_c.rb >> [...] >> ...etc... >> >> ...should become something (**speedier) like this: >> >> rails g model_a name:string [...], model_b name:string [...], >> model_c name:string [...] ...**etc... >> >> invoke active_record >> create db/migrate/**201302... >> create app/models/**model_a.rb >> [...] >> create db/migrate/**201302... >> create app/models/**model_b.rb >> [...] >> create db/migrate/**201302... >> create app/models/**model_c.rb >> [...] >> ...etc... >> > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to rubyonrails-core+unsubscribe@googlegroups.com. > To post to this group, send email to rubyonrails-core@googlegroups.com. > Visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > >-- At. Carlos Antonio -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscribe@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Pete
2013-Feb-24 13:35 UTC
Re: Re: Model generator: Invoke active_record only 1x for mulitiple models?
Thanks a lot for the feedback, guys! This is awesome! Really looking forward to seeing that in Rails! On Saturday, February 23, 2013 11:30:57 PM UTC+1, Carlos Antonio da Silva wrote:> > Yes, zeus is a nice one to speed up development lifecycle. There''s also > spring <http://github.com/jonleighton/spring>, a new tool from > jonleighton that''s under test and is likely to be the default integration > with Rails as part of the development process, I recommend you guys to take > a look. > > Pete, I think the path that zeus and spring are taking is the way to go, > since it does not help only with model generators, but speeds up > generators, console, tests, and everything else related to our development > workflow. > > > On Sat, Feb 23, 2013 at 4:48 PM, Borna Novak <dosad...@gmail.com<javascript:> > > wrote: > >> Pete, >> >> this project saved a couple of years of my life already: >> https://github.com/burke/zeus >> >> Basically, it runs rake jobs, generators, destroyers, tests... in under a >> second by preloading the various environments and then just forking an >> appropriate existing process when a command is triggered, real life-saver >> >> >> Borna >> >> >> On Friday, February 22, 2013 5:37:36 PM UTC+1, Pete wrote: >>> >>> Currently (3.2.12), Rails needs 1 separate command per model/migration >>> to be generated. Each such "**rails g ..." command invokes **active_record once. >>> >>> >>> When a project needs to generate a larger number of models/migrations, >>> this process can take up lots **of time. >>> >>> So, this... >>> >>> rails g model_a name:**string [...] >>> rails g model_b name:**string [...] >>> rails g model_c name:**string [...] >>> ...etc... >>> >>> invoke active_record >>> create db/migrate/**201302... >>> create app/models/**model_a.rb >>> [...] >>> invoke active_record >>> create db/migrate/**201302... >>> create app/models/**model_b.rb >>> [...] >>> invoke active_record >>> create db/migrate/**201302... >>> create app/models/**model_c.rb >>> [...] >>> ...etc... >>> >>> ...should become something (**speedier) like this: >>> >>> rails g model_a name:string [...], model_b name:string [...], >>> model_c name:string [...] ...**etc... >>> >>> invoke active_record >>> create db/migrate/**201302... >>> create app/models/**model_a.rb >>> [...] >>> create db/migrate/**201302... >>> create app/models/**model_b.rb >>> [...] >>> create db/migrate/**201302... >>> create app/models/**model_c.rb >>> [...] >>> ...etc... >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ruby on Rails: Core" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to rubyonrails-co...@googlegroups.com <javascript:>. >> To post to this group, send email to rubyonra...@googlegroups.com<javascript:> >> . >> Visit this group at http://groups.google.com/group/rubyonrails-core?hl=en >> . >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > > -- > At. > Carlos Antonio >-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscribe@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Carlos Antonio da Silva
2013-Feb-24 13:36 UTC
Re: Re: Model generator: Invoke active_record only 1x for mulitiple models?
For now you can just install the gem (like spring) and use its commands in any 3.x app, it doesn''t even need to be in your Gemfile. Check its readme for more info. On Sun, Feb 24, 2013 at 10:35 AM, Pete <peter.winklr@gmail.com> wrote:> Thanks a lot for the feedback, guys! > > This is awesome! Really looking forward to seeing that in Rails! > > > On Saturday, February 23, 2013 11:30:57 PM UTC+1, Carlos Antonio da Silva > wrote: > >> Yes, zeus is a nice one to speed up development lifecycle. There''s also >> spring <http://github.com/jonleighton/spring>, a new tool from >> jonleighton that''s under test and is likely to be the default integration >> with Rails as part of the development process, I recommend you guys to take >> a look. >> >> Pete, I think the path that zeus and spring are taking is the way to go, >> since it does not help only with model generators, but speeds up >> generators, console, tests, and everything else related to our development >> workflow. >> >> >> On Sat, Feb 23, 2013 at 4:48 PM, Borna Novak <dosad...@gmail.com> wrote: >> >>> Pete, >>> >>> this project saved a couple of years of my life already: >>> https://github.com/burke/zeus >>> >>> Basically, it runs rake jobs, generators, destroyers, tests... in under >>> a second by preloading the various environments and then just forking an >>> appropriate existing process when a command is triggered, real life-saver >>> >>> >>> Borna >>> >>> >>> On Friday, February 22, 2013 5:37:36 PM UTC+1, Pete wrote: >>>> >>>> Currently (3.2.12), Rails needs 1 separate command per model/migration >>>> to be generated. Each such "**ra**ils g ..." command invokes **act**ive_record once. >>>> >>>> >>>> When a project needs to generate a larger number of models/migrations, >>>> this process can take up lots ****of time. >>>> >>>> So, this... >>>> >>>> rails g model_a name:**strin**g [...] >>>> rails g model_b name:**strin**g [...] >>>> rails g model_c name:**strin**g [...] >>>> ...etc... >>>> >>>> invoke active_record >>>> create db/migrate/**20130**2... >>>> create app/models/**model**_a.rb >>>> [...] >>>> invoke active_record >>>> create db/migrate/**20130**2... >>>> create app/models/**model**_b.rb >>>> [...] >>>> invoke active_record >>>> create db/migrate/**20130**2... >>>> create app/models/**model**_c.rb >>>> [...] >>>> ...etc... >>>> >>>> ...should become something (**sp**eedier) like this: >>>> >>>> rails g model_a name:string [...], model_b name:string [...], >>>> model_c name:string [...] ...**e**tc... >>>> >>>> invoke active_record >>>> create db/migrate/**20130**2... >>>> create app/models/**model**_a.rb >>>> [...] >>>> create db/migrate/**20130**2... >>>> create app/models/**model**_b.rb >>>> [...] >>>> create db/migrate/**20130**2... >>>> create app/models/**model**_c.rb >>>> [...] >>>> ...etc... >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Ruby on Rails: Core" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to rubyonrails-co...@**googlegroups.com. >>> To post to this group, send email to rubyonra...@googlegroups.**com. >>> >>> Visit this group at http://groups.google.com/** >>> group/rubyonrails-core?hl=en<http://groups.google.com/group/rubyonrails-core?hl=en> >>> . >>> For more options, visit https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>> . >>> >>> >>> >> >> >> >> -- >> At. >> Carlos Antonio >> > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to rubyonrails-core+unsubscribe@googlegroups.com. > To post to this group, send email to rubyonrails-core@googlegroups.com. > Visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > >-- At. Carlos Antonio -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscribe@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Duncan Beevers
2013-Feb-24 17:40 UTC
Re: Re: Model generator: Invoke active_record only 1x for mulitiple models?
This seems really cool. Is Spring appropriate running on production servers? For example, on deploy, many different rake tasks may be invoked (asset compilation, database migrations, etc...) and having something like this spawned could result in a significant speed-up. On Sun, Feb 24, 2013 at 7:36 AM, Carlos Antonio da Silva < carlosantoniodasilva@gmail.com> wrote:> For now you can just install the gem (like spring) and use its commands in > any 3.x app, it doesn''t even need to be in your Gemfile. Check its readme > for more info. > > > On Sun, Feb 24, 2013 at 10:35 AM, Pete <peter.winklr@gmail.com> wrote: > >> Thanks a lot for the feedback, guys! >> >> This is awesome! Really looking forward to seeing that in Rails! >> >> >> On Saturday, February 23, 2013 11:30:57 PM UTC+1, Carlos Antonio da Silva >> wrote: >> >>> Yes, zeus is a nice one to speed up development lifecycle. There''s also >>> spring <http://github.com/jonleighton/spring>, a new tool from >>> jonleighton that''s under test and is likely to be the default integration >>> with Rails as part of the development process, I recommend you guys to take >>> a look. >>> >>> Pete, I think the path that zeus and spring are taking is the way to go, >>> since it does not help only with model generators, but speeds up >>> generators, console, tests, and everything else related to our development >>> workflow. >>> >>> >>> On Sat, Feb 23, 2013 at 4:48 PM, Borna Novak <dosad...@gmail.com> wrote: >>> >>>> Pete, >>>> >>>> this project saved a couple of years of my life already: >>>> https://github.com/burke/zeus >>>> >>>> Basically, it runs rake jobs, generators, destroyers, tests... in under >>>> a second by preloading the various environments and then just forking an >>>> appropriate existing process when a command is triggered, real life-saver >>>> >>>> >>>> Borna >>>> >>>> >>>> On Friday, February 22, 2013 5:37:36 PM UTC+1, Pete wrote: >>>>> >>>>> Currently (3.2.12), Rails needs 1 separate command per model/migration >>>>> to be generated. Each such "**ra**ils g ..." command invokes **act**ive_record once. >>>>> >>>>> >>>>> When a project needs to generate a larger number of models/migrations, >>>>> this process can take up lots ****of time. >>>>> >>>>> So, this... >>>>> >>>>> rails g model_a name:**strin**g [...] >>>>> rails g model_b name:**strin**g [...] >>>>> rails g model_c name:**strin**g [...] >>>>> ...etc... >>>>> >>>>> invoke active_record >>>>> create db/migrate/**20130**2... >>>>> create app/models/**model**_a.rb >>>>> [...] >>>>> invoke active_record >>>>> create db/migrate/**20130**2... >>>>> create app/models/**model**_b.rb >>>>> [...] >>>>> invoke active_record >>>>> create db/migrate/**20130**2... >>>>> create app/models/**model**_c.rb >>>>> [...] >>>>> ...etc... >>>>> >>>>> ...should become something (**sp**eedier) like this: >>>>> >>>>> rails g model_a name:string [...], model_b name:string [...], >>>>> model_c name:string [...] ...**e**tc... >>>>> >>>>> invoke active_record >>>>> create db/migrate/**20130**2... >>>>> create app/models/**model**_a.rb >>>>> [...] >>>>> create db/migrate/**20130**2... >>>>> create app/models/**model**_b.rb >>>>> [...] >>>>> create db/migrate/**20130**2... >>>>> create app/models/**model**_c.rb >>>>> [...] >>>>> ...etc... >>>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Ruby on Rails: Core" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to rubyonrails-co...@**googlegroups.com. >>>> To post to this group, send email to rubyonra...@googlegroups.**com. >>>> >>>> Visit this group at http://groups.google.com/** >>>> group/rubyonrails-core?hl=en<http://groups.google.com/group/rubyonrails-core?hl=en> >>>> . >>>> For more options, visit https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>>> . >>>> >>>> >>>> >>> >>> >>> >>> -- >>> At. >>> Carlos Antonio >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ruby on Rails: Core" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to rubyonrails-core+unsubscribe@googlegroups.com. >> To post to this group, send email to rubyonrails-core@googlegroups.com. >> Visit this group at http://groups.google.com/group/rubyonrails-core?hl=en >> . >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > > -- > At. > Carlos Antonio > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to rubyonrails-core+unsubscribe@googlegroups.com. > To post to this group, send email to rubyonrails-core@googlegroups.com. > Visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > >-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscribe@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Borna Novak
2013-Feb-25 08:57 UTC
Re: Re: Model generator: Invoke active_record only 1x for mulitiple models?
I usually make a deployment rake task and spawn other tasks from there, this way you save up on environment load times so zeus / spring bring no added benefit (only added unknowns). Also see the "rake multitask" feature (http://stackoverflow.com/questions/5606290/how-do-i-launch-multiple-rakes-in-parallel-from-a-ruby-script) Borna On Sunday, February 24, 2013 6:40:32 PM UTC+1, duncanbeevers wrote:> > This seems really cool. Is Spring appropriate running on production > servers? For example, on deploy, many different rake tasks may be invoked > (asset compilation, database migrations, etc...) and having something like > this spawned could result in a significant speed-up. > > On Sun, Feb 24, 2013 at 7:36 AM, Carlos Antonio da Silva < > carlosanto...@gmail.com <javascript:>> wrote: > >> For now you can just install the gem (like spring) and use its commands >> in any 3.x app, it doesn''t even need to be in your Gemfile. Check its >> readme for more info. >> >> >> On Sun, Feb 24, 2013 at 10:35 AM, Pete <peter....@gmail.com <javascript:> >> > wrote: >> >>> Thanks a lot for the feedback, guys! >>> >>> This is awesome! Really looking forward to seeing that in Rails! >>> >>> >>> On Saturday, February 23, 2013 11:30:57 PM UTC+1, Carlos Antonio da >>> Silva wrote: >>> >>>> Yes, zeus is a nice one to speed up development lifecycle. There''s also >>>> spring <http://github.com/jonleighton/spring>, a new tool from >>>> jonleighton that''s under test and is likely to be the default integration >>>> with Rails as part of the development process, I recommend you guys to take >>>> a look. >>>> >>>> Pete, I think the path that zeus and spring are taking is the way to >>>> go, since it does not help only with model generators, but speeds up >>>> generators, console, tests, and everything else related to our development >>>> workflow. >>>> >>>> >>>> On Sat, Feb 23, 2013 at 4:48 PM, Borna Novak <dosad...@gmail.com>wrote: >>>> >>>>> Pete, >>>>> >>>>> this project saved a couple of years of my life already: >>>>> https://github.com/burke/zeus >>>>> >>>>> Basically, it runs rake jobs, generators, destroyers, tests... in >>>>> under a second by preloading the various environments and then just forking >>>>> an appropriate existing process when a command is triggered, real life-saver >>>>> >>>>> >>>>> Borna >>>>> >>>>> >>>>> On Friday, February 22, 2013 5:37:36 PM UTC+1, Pete wrote: >>>>>> >>>>>> Currently (3.2.12), Rails needs 1 separate command per >>>>>> model/migration to be generated. Each such "**ra** >>>>>> ils g ..." command invokes **act**ive_record once. >>>>>> >>>>>> When a project needs to generate a larger number of >>>>>> models/migrations, this process can take up lots ****of time. >>>>>> >>>>>> So, this... >>>>>> >>>>>> rails g model_a name:**strin**g [...] >>>>>> rails g model_b name:**strin**g [...] >>>>>> rails g model_c name:**strin**g [...] >>>>>> ...etc... >>>>>> >>>>>> invoke active_record >>>>>> create db/migrate/**20130**2... >>>>>> create app/models/**model**_a.rb >>>>>> [...] >>>>>> invoke active_record >>>>>> create db/migrate/**20130**2... >>>>>> create app/models/**model**_b.rb >>>>>> [...] >>>>>> invoke active_record >>>>>> create db/migrate/**20130**2... >>>>>> create app/models/**model**_c.rb >>>>>> [...] >>>>>> ...etc... >>>>>> >>>>>> ...should become something (**sp**eedier) like this: >>>>>> >>>>>> rails g model_a name:string [...], model_b name:string [...], >>>>>> model_c name:string [...] ...**e**tc... >>>>>> >>>>>> invoke active_record >>>>>> create db/migrate/**20130**2... >>>>>> create app/models/**model**_a.rb >>>>>> [...] >>>>>> create db/migrate/**20130**2... >>>>>> create app/models/**model**_b.rb >>>>>> [...] >>>>>> create db/migrate/**20130**2... >>>>>> create app/models/**model**_c.rb >>>>>> [...] >>>>>> ...etc... >>>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Ruby on Rails: Core" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to rubyonrails-co...@**googlegroups.com. >>>>> To post to this group, send email to rubyonra...@googlegroups.**com. >>>>> >>>>> Visit this group at http://groups.google.com/** >>>>> group/rubyonrails-core?hl=en<http://groups.google.com/group/rubyonrails-core?hl=en> >>>>> . >>>>> For more options, visit https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>>>> . >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> At. >>>> Carlos Antonio >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Ruby on Rails: Core" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to rubyonrails-co...@googlegroups.com <javascript:>. >>> To post to this group, send email to rubyonra...@googlegroups.com<javascript:> >>> . >>> Visit this group at >>> http://groups.google.com/group/rubyonrails-core?hl=en. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> >> >> -- >> At. >> Carlos Antonio >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ruby on Rails: Core" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to rubyonrails-co...@googlegroups.com <javascript:>. >> To post to this group, send email to rubyonra...@googlegroups.com<javascript:> >> . >> Visit this group at http://groups.google.com/group/rubyonrails-core?hl=en >> . >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > >-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscribe@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. For more options, visit https://groups.google.com/groups/opt_out.