Ruby on Rails

Colin Law <clanlaw@gmail.com> writes:

> On 31 Dec 2015 14:10, "'krfg' via Ruby on Rails: Talk" <
> rubyonrails-talk@googlegroups.com> wrote:
>>
>> Well, so thank you for helping me and supporting me up to the solution.
>> I am already looking for and reading documentation on transactions,
>> sequences and truncations in Postgres, which is new stuff for me. My next
>> goal is finding how to reset the id sequence in Postgres.
>
> Why? As I said before you should not use the id as a numeric value.
>
> Colin

Even further, there are reasons to completely and absolutely ignore
and never even expose the id column for a record, and prefer a UUID
instead. Some of these include:

- you can't count on it being the same across databases if you even need
to migrate your data

- exposing it to the user can reveal more information about your app
than you want ("oh, there's only 550 people signed up, this must be
useless")

- exposing it to the user can open avenues of attack you don't want to
open

- id 1 *must* be the admin, so we'll concentrate our attacks there


The emphasis you seem to be showing is causing me to scratch my
head. Why is starting at so absolutely important to you? It is a proper
error to count on a particular record always have an absolute record id
value.

--
Tamara Temple
tamouse@gmail.com
http://www.tamouse.org

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/m2ziwqdr9b.fsf%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

On 31 Dec 2015 14:10, "'krfg' via Ruby on Rails: Talk" <rubyonrails-talk@googlegroups.com> wrote:
>
> Well, so thank you for helping me and supporting me up to the solution.
> I am already looking for and reading documentation on transactions, sequences and truncations in Postgres, which is new stuff for me. My next goal is finding how to reset the id sequence in Postgres.

Why? As I said before you should not use the id as a numeric value.

Colin

>
> I seize the opportunity to wish you all a happy new year.
>
> --
> You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
> To post to this group, send email to rubyonrails-talk@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/a3d59189-ad1f-4e64-a5d9-7145532695fb%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

'krfg' via Ruby on Rails: Talk <rubyonrails-talk@googlegroups.com> writes:

> On Tuesday, December 29, 2015 at 7:31:36 PM UTC+1, tamouse wrote:
>>
>>
>> >> What happened when you tried creating a new test application?
>> >>
>>
>> The problem as you've stated it is that your first user gets id=2. The
>> point of the test is to find the minimum set of conditions that
>> reproduce that behaviour so you can see why it's happening...
>
> ... Then prepare the app for heroku, create a new app at heroku for
>> this test app, and run it on heroku and see what happens
>
>
> I just finished to create a new test app as you suggested.
> In the test app too first user created got id 2 instead of 1, and there is
> no user with id 1.
> I am really puzzled...
>
> I recreated the same conditions of the former application, following the
> same steps.
> However I did not repeated the error of duplicating the User model and of
> migrating the migration in any topic branch. This means that what is
> creating the issue is something else.
>
> I used a new, totally separated public workspace at Colud9.
>
> I tried to figure out what can causing the issue and found just 2 possible
> explanations:
>
> 1. I added a new user in my development environment at Cloud9 and deployed
> at Heroku without resetting the database at Cloud9
> 2. I added a new user at Heroku with the console in sandbox mode.

This is it, exactly. Sandbox mode inserts the record, but since it's
running in a transaction, the table is then truncated. Table truncation
in Postgres does not reset the id sequence without a specific directive
to do so.

> Point 2 could explain what Colin Law previously suggested, that is that id
> numbers are not reused: is it possible that this rule is effective even
> when the user is created with the console in a sandbox mode?



--
Tamara Temple
tamouse@gmail.com
http://www.tamouse.org

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/m237uig7hi.fsf%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

On Wednesday, December 30, 2015 at 10:30:40 PM UTC, James Jelinek wrote:
> Sandbox won't persist data. It'll do a transactional rollback. It never really persists data. 
>
>
As I said earlier, rolling back transactions doesn't reset sequences on Postgres ( http://www.postgresql.org/docs/current/static/functions-sequence.html). Creating a record in the sandbox would create a gap in the id sequence.

Fred

> But your quirk is interesting.  I've tried duplicating it and cannot. 
>
> Sent from my iPhone
>
> On Dec 30, 2015, at 4:26 PM, 'krfg' via Ruby on Rails: Talk <rubyonrails-talk@googlegroups.com> wrote:
>
>
>
>
> On Tuesday, December 29, 2015 at 7:31:36 PM UTC+1, tamouse wrote:
>
> >> What happened when you tried creating a new test application?
>
> >>
>
>
> The problem as you've stated it is that your first user gets id=2. The
>
> point of the test is to find the minimum set of conditions that
>
> reproduce that behaviour so you can see why it's happening...... Then prepare the app for heroku, create a new app at heroku for
>
> this test app, and run it on heroku and see what happens
>
> I just finished to create a new test app as you suggested.
> In the test app too first user created got id 2 instead of 1, and there is no user with id 1.
> I am really puzzled...
>
> I recreated the same conditions of the former application, following the same steps.
> However I did not repeated the error of duplicating the User model and of migrating the migration in any topic branch. This means that what is creating the issue is something else.
>
> I used a new, totally separated public workspace at Colud9.
>
> I tried to figure out what can causing the issue and found just 2 possible explanations:
>
> 1. I added a new user in my development environment at Cloud9 and deployed at Heroku without resetting the database at Cloud9
> 2. I added a new user at Heroku with the console in sandbox mode.
>
> Point 2 could explain what Colin Law previously suggested, that is that id numbers are not reused: is it possible that this rule is effective even when the user is created with the console in a sandbox mode?
>
>
>
>
>
>
>
> --
>
> You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
>
> To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
>
> To post to this group, send email to rubyonrails-talk@googlegroups.com.
>
> To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/3246c189-392c-4bef-a12a-b8b51174032a%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/e8ad57b3-fff8-48d7-b2d2-3d10389d85ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

On Wednesday, December 30, 2015 at 9:25:01 PM UTC, Torsten Rüger wrote:
> Thanks Fred,
>
>
> strange to think there should be an error that can't be handled in rails. Still, thanks for the answer, which i am unfortunately not sure i understand.

You could also handle via a rack middleware or by supplying a custom exception app (see http://guides.rubyonrails.org/configuring.html#rails-general-configuration)
>
>
> Are you saying i should have  a
> <Limit CONNECT>
>
>
> </Limit>
>

Not sure - never done this, but this seems to be the mechanism Apache provides for filtering requests based on http method.

Fred


> On Tuesday, 29 December 2015 21:29:00 UTC+2, Frederick Cheung wrote:On Tuesday, December 29, 2015 at 6:13:52 PM UTC, Torsten Rüger wrote:
>
> > Hi,
>
> >
>
> >
>
> > i've been getting the subject error for some while in production. 
>
> > I've tried to find out what that connect even means with little avail. 
>
> > But i was generally surprised how much hacking attempts are being made, so i'm pretty sure it's ill intent.
>
>
>
> CONNECT is an http method used for proxies to allow tunnelling arbitrary traffic through a proxy: basically someone has been scanning for misconfigured proxies (and probably other stuff too). Just a fact of life really.
>
> >
>
> >
>
> > Just, i can't seems to get rid of the error. I tried to add rescue_from to my ApplicationController, as in:
>
> >
>
> >
>
> >
>
> >   rescue_from ActionController::RoutingError, with: :error_404
>
> >
>
> >
>
>
>
> This type of routing error can't be rescued like that since rails doesn't know which controller should be used. If it bothers you then you could try blocking it at the webserver level (eg https://httpd.apache.org/docs/2.4/mod/core.html#limit)
>
>
>
> Fred
>
>
>
> > but that doesn't do it. The call goes from phusion through rack and rails, and ends in 
>
> > actionpack-4.2.5/lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call'
>
> >
>
> >
>
> >
>
> > Has anyone encountered this in the wild ?
>
> >
>
> >
>
> > Torsten

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/9420ff91-711f-47a8-a958-6b8bf373eb8f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

On Tuesday, December 29, 2015 at 7:31:36 PM UTC+1, tamouse wrote:

>> What happened when you tried creating a new test application?
>>

The problem as you've stated it is that your first user gets id=2. The
point of the test is to find the minimum set of conditions that
reproduce that behaviour so you can see why it's happening...

... Then prepare the app for heroku, create a new app at heroku for
this test app, and run it on heroku and see what happens

I just finished to create a new test app as you suggested.
In the test app too first user created got id 2 instead of 1, and there is no user with id 1.
I am really puzzled...

I recreated the same conditions of the former application, following the same steps.
However I did not repeated the error of duplicating the User model and of migrating the migration in any topic branch. This means that what is creating the issue is something else.

I used a new, totally separated public workspace at Colud9.

I tried to figure out what can causing the issue and found just 2 possible explanations:

1. I added a new user in my development environment at Cloud9 and deployed at Heroku without resetting the database at Cloud9
2. I added a new user at Heroku with the console in sandbox mode.

Point 2 could explain what Colin Law previously suggested, that is that id numbers are not reused: is it possible that this rule is effective even when the user is created with the console in a sandbox mode?

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/3246c189-392c-4bef-a12a-b8b51174032a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

On Tuesday, 29 December 2015 16:28:32 UTC-5, Michael Prieto wrote:

Hello everyone o/

I'm currently building a Rails app and I'm using Devise and Omniauth (Google OAuth2 and Facebook) for authentication. All users are going to have unique usernames. This is not a problem when I'm using just a form, but when the users tries to sign up using Omniauth, I can't get a username that I can ensure is unique and fits the criteria I've made for a valid username. If I do try to sign up with it, it just redirects to the form that regular users would use to sign up.

I've thought about redirecting the user to a separate page where they create a username, but I don't know how I would go about this. Searching the internet has not yielded any results either. 

Does anyone know how I could accomplish this? I'm open to any ideas.

Yeah you have to specify the version number prior to the "new" verb.  I think this is especially important when you have multiple versions of the Rails gem installed on your system.

On 30 Dec 2015 03:16, "fugee ohu" <fugee279@gmail.com> wrote:
>
> if users has one profile and profiles has many schools should i be able to see schools at u.profiles.schools where u is a user object

No u.profiles is effectively an array. Have a look at has many through.

Colin

>
> --
> You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
> To post to this group, send email to rubyonrails-talk@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/75bfbbf7-dc86-41ed-9658-50cc7a6138f7%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

 thanks

On Tuesday, December 29, 2015 at 8:51:13 PM UTC-5, Walter Lee Davis wrote:

> On Dec 29, 2015, at 6:25 PM, fugee ohu <fuge...@gmail.com> wrote:
>
> i'm using devise for users,  how do i let a user change his password?

Send them to /users/password/new and they will be able to reset their password. There's a whole system in there that sends an e-mail with a login token to the registered account address.

Walter

>
> --
> You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-ta...@googlegroups.com.
> To post to this group, send email to rubyonra...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/e7da42f6-3a98-4c60-8e69-e2bbf77eb71c%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

> On Dec 29, 2015, at 7:27 PM, fugee ohu <fugee279@gmail.com> wrote:
>
> Can you tell me how to display an attribute from the parent in a view please

Show your work! What have you tried already?

Walter

>
> On Tuesday, December 29, 2015 at 8:47:59 AM UTC-5, Walter Lee Davis wrote:
>
> > On Dec 29, 2015, at 8:36 AM, fugee ohu <fuge...@gmail.com> wrote:
> >
> > user has many addresses so i wanna put address fields in the new user registration form, i don't know how i would do it, i'm trying to conceptualize it
> >
>
> Have a look at accepts_nested_attributes_for and the fields_for form helper. This is a really well-solved problem in Rails. If you use simple_form, there are helpers in there for this pattern as well. And as usual, Ryan Bates wrote about this (and made a great gem for it) about a million internet-years ago: https://github.com/ryanb/nested_form and http://railscasts.com/episodes/196-nested-model-form-revised
>
> Walter
>
> > --
> > You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
> > To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-ta...@googlegroups.com.
> > To post to this group, send email to rubyonra...@googlegroups.com.
> > To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/5898a890-523e-48b2-bf2e-0d12d992c18c%40googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
> To post to this group, send email to rubyonrails-talk@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/bd965c24-fcdd-401b-9b93-859532f97851%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/3E3655BF-E34D-47E4-9AE0-11AC1BCD59B1%40wdstudio.com.
For more options, visit https://groups.google.com/d/optout.

> On Dec 29, 2015, at 6:25 PM, fugee ohu <fugee279@gmail.com> wrote:
>
> i'm using devise for users, how do i let a user change his password?

Send them to /users/password/new and they will be able to reset their password. There's a whole system in there that sends an e-mail with a login token to the registered account address.

Walter

>
> --
> You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
> To post to this group, send email to rubyonrails-talk@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/e7da42f6-3a98-4c60-8e69-e2bbf77eb71c%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/ABA20C3F-1674-4A97-BB7D-86DB7E5D6430%40wdstudio.com.
For more options, visit https://groups.google.com/d/optout.

On Tuesday, December 29, 2015 at 6:13:52 PM UTC, Torsten Rüger wrote:
> Hi,
>
>
> i've been getting the subject error for some while in production. 
> I've tried to find out what that connect even means with little avail. 
> But i was generally surprised how much hacking attempts are being made, so i'm pretty sure it's ill intent.

CONNECT is an http method used for proxies to allow tunnelling arbitrary traffic through a proxy: basically someone has been scanning for misconfigured proxies (and probably other stuff too). Just a fact of life really.
>
>
> Just, i can't seems to get rid of the error. I tried to add rescue_from to my ApplicationController, as in:
>
>
>
>   rescue_from ActionController::RoutingError, with: :error_404
>
>

This type of routing error can't be rescued like that since rails doesn't know which controller should be used. If it bothers you then you could try blocking it at the webserver level (eg https://httpd.apache.org/docs/2.4/mod/core.html#limit)

Fred

> but that doesn't do it. The call goes from phusion through rack and rails, and ends in 
> actionpack-4.2.5/lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call'
>
>
>
> Has anyone encountered this in the wild ?
>
>
> Torsten

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/29ce48c7-c68d-4b29-ab7f-cf80519ed91a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Nojin Park <hourglassxe@gmail.com> writes:

> Hi all,
>
> I've started learning Ruby and I'm still learning the basics.
> My goal is to create web applications using rails and multiple API's (API
> mashup.. Google, FB, Twitter,etc...)

Welcome!

> I see most people coding in Java script when communicating with API's and I
> have 2 questions.
>
> 1. Is learning java script the only option to communicate with API's?
> 2. If yes, do I need to learn entire java script? or just learning small
> basic portion will still do the work?
>
> I have no "real coding experience" but have pretty good understanding about
> how the web works under the hood.
> Thanks in advance :)
>
> E

The answer to this is, to my mind, you code in the language of your
application. If you application is written in JS, you write in JS; as
your application is written using Rails, you write in Ruby.

What's possibly confusing the issue is that many public APIs as you have
listed transmit responses in JSON, which is a JS object. However, every
language used to communicate with web services has the ability to
understand that, including Ruby.

In addition, Rails has a tonne of contributed gems to interface with the
popular web services.

That said, you'll still probably need to learn some JS along the way
anyway because it's pretty much expected your own application front end
will need to use some.

Take it slow, learn in stages; there's a lot to learn and you should
expect it to take some time.

--
Tamara Temple
tamouse@gmail.com
http://www.tamouse.org

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/m2h9j1qeud.fsf%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

'krfg' via Ruby on Rails: Talk <rubyonrails-talk@googlegroups.com> writes:

> On Tuesday, December 29, 2015 at 4:38:47 AM UTC+1, tamouse wrote:
>>
>>
>>
>> What happened when you tried creating a new test application?
>>
>>
> I am sorry but if you do not mind I need some instruction on how to
> recreate same conditions in a test app. I feel and am a bit awkward at this
> stage.
> As far as I understood you want me to create a test app with sign up page,
> see if it works and then recreate the issue that the original app is having.

The problem as you've stated it is that your first user gets id=2. The
point of the test is to find the minimum set of conditions that
reproduce that behaviour so you can see why it's happening. My thought
was (and this is just what I did) to in a new directory, simply run the
rails new command to create a new rails app, generate a scaffold with a
model with one field, and check what happens locally to make sure it
works. Then prepare the app for heroku, create a new app at heroku for
this test app, and run it on heroku and see what happens. Then
progressively add to the test app until or if you see the same behaviour of
the first user id starting at 2 instead of 1. However, as you've shown,
regular heroku users don't have the permission to drop the database and
recreate it, which makes it a bit more complex. As an alternative to
that, you can instead destroy the heroku app and create another.

> I am using Cloud9 as a development environment, and I am working on a
> private workspace.
> Cloud9 provides free accounts with only 1 private workspace and unlimited
> public workspaces.
> I may choose to create a new public workspace for my test app or using the
> same workspace I have been using so far and which is hosting 3 different
> apps overall.
> What solution best suits me?

I have no idea what best suits you in this scenario; it's really up to
you. I think, though, you may just be overthinking this. It's just a
test app, it's not going to be around long, does it really matter?

The only possible consideration I would have, is that since you are
publicy sharing with us this problem, if you put it on a public
workspace, there's just the possibility that someone else can pair with
you, look at it, and possibly spot the issue.

> I also have to consider that free accounts at Heroku allow only 5 apps, but
> I suppose I can eventually destroy my test app both in my workspace and at
> Heroku.

You can create and destroy heroku apps many times a day, really.

Here's the thing about this: in every test I've personally run to try to
recreate your problem, I've never been able to reproduce it. It's
definitely not an issue strictly with heroku, rails, or postgres, that I
can find. At this point, since you are not deleting your data base, I'm
quite unsure how you are even getting them to consistently start at 2
instead of 1, or really by this time, depending on how many times you've
tested this, even higher numbers.

--
Tamara Temple
tamouse@gmail.com
http://www.tamouse.org

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/m2io3hqf8c.fsf%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

> On Dec 29, 2015, at 8:36 AM, fugee ohu <fugee279@gmail.com> wrote:
>
> user has many addresses so i wanna put address fields in the new user registration form, i don't know how i would do it, i'm trying to conceptualize it
>

Have a look at accepts_nested_attributes_for and the fields_for form helper. This is a really well-solved problem in Rails. If you use simple_form, there are helpers in there for this pattern as well. And as usual, Ryan Bates wrote about this (and made a great gem for it) about a million internet-years ago: https://github.com/ryanb/nested_form and http://railscasts.com/episodes/196-nested-model-form-revised

Walter

> --
> You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
> To post to this group, send email to rubyonrails-talk@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/5898a890-523e-48b2-bf2e-0d12d992c18c%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/176C439F-A99E-40BA-8031-E97EC970DD66%40wdstudio.com.
For more options, visit https://groups.google.com/d/optout.