On Apr 8, 4:38 pm, Marian Steinbach <[email protected]> wrote: > It seems as if I am having trouble with Rails automatically wrapping > multiple SQL INSERT statements into BEGIN and COMMIT. > > Is there a way to prevent Rails from doing this?
That sounds like a code smell. :-) See below. > I want to create a user object when creating some other object and > asign the user to that one. And then finally I want to log in that > Users (authlogic). All in one step. But it appears as if the new user > record gets no ID, since not yet written, and thus cannot be assigned > to the rest. How about creating the first Model, then the User model, and then after that is setup, do the login? Ho-Sheng Hsiao http://hosheng.blogspot.com -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
