thr3ads.net - Rails - Storing ActiveRecords in the Session [Jan 2007]

If this information is useful, please help other people find it:
Share via:

Robert Head

2007-Jan-25 23:31 UTC

Storing ActiveRecords in the Session

Is there a secret to successfully storing ActiveRecords in the Session
(which is being stored in the DB) without getting marshalling
exceptions?

-- 
Posted via http://www.ruby-forum.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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Peter Ertl

2007-Jan-26 11:33 UTC

head link

Re: Storing ActiveRecords in the Session

just store the primary key of the record... that''s usually much better

2007/1/26, Robert Head
<rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org>:>
>
> Is there a secret to successfully storing ActiveRecords in the Session
> (which is being stored in the DB) without getting marshalling
> exceptions?
>
> --
> Posted via http://www.ruby-forum.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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Robert Head

2007-Jan-26 21:57 UTC

head link

Re: Storing ActiveRecords in the Session

Peter Ertl wrote:> just store the primary key of the record... that''s usually much
better
> 
Sure, but then I have to hit the DB *every time* I use it, no?

-- 
Posted via http://www.ruby-forum.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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Tom Mornini

2007-Jan-26 22:04 UTC

head link

Re: Storing ActiveRecords in the Session

On Jan 26, 2007, at 1:57 PM, Robert Head wrote:
> Peter Ertl wrote:
>> just store the primary key of the record... that''s usually
much
>> better
>
> Sure, but then I have to hit the DB *every time* I use it, no?
No, it''s relatively easy to make sure the ''penalty''
is once per page
that uses it.

The session is likely a DB hit in any case (ActiveRecordStore), and  
if you put an
entire AR model in it, it makes this session DB hit a monster each  
and every page.

Storing the ID makes sure that your AR model isn''t stale, too.

-- 
-- Tom Mornini, CTO
-- Engine Yard, Ruby on Rails Hosting
-- Reliability, Ease of Use, Scalability
-- (866) 518-YARD (9273)


--~--~---------~--~----~------------~-------~--~----~
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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Robert Head

2007-Jan-31 20:28 UTC

head link

Re: Storing ActiveRecords in the Session

Tom Mornini wrote:> On Jan 26, 2007, at 1:57 PM, Robert Head wrote:
> 
>> Peter Ertl wrote:
>>> just store the primary key of the record... that''s usually
much
>>> better
>>
>> Sure, but then I have to hit the DB *every time* I use it, no?
> 
> No, it''s relatively easy to make sure the
''penalty'' is once per page
> that uses it.
OK, exactly.  So, what is the "relatively easy" way to make sure the 
object is only loaded once per page?

- Still perplexed

-- 
Posted via http://www.ruby-forum.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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Ezra Zygmuntowicz

2007-Jan-31 21:51 UTC

head link

Re: Storing ActiveRecords in the Session

On Jan 31, 2007, at 12:28 PM, Robert Head wrote:
>
> Tom Mornini wrote:
>> On Jan 26, 2007, at 1:57 PM, Robert Head wrote:
>>
>>> Peter Ertl wrote:
>>>> just store the primary key of the record... that''s
usually much
>>>> better
>>>
>>> Sure, but then I have to hit the DB *every time* I use it, no?
>>
>> No, it''s relatively easy to make sure the
''penalty'' is once per page
>> that uses it.
>
> OK, exactly.  So, what is the "relatively easy" way to make sure
the
> object is only loaded once per page?
>
> - Still perplexed
>
> --  
> Posted via http://www.ruby-forum.com/.

   def current_user
     @current_user ||= session[:user_id] ? User.find_by_id(session 
[:user_id]) : nil
   end

This will cache the the user in @current_user so you can call  
current_user multiple times during a request and it will only hit the  
db once.

Cheers-
-- Ezra Zygmuntowicz 
-- Lead Rails Evangelist
-- ez-NLltGlunAUd/unjJdyJNww@public.gmane.org
-- Engine Yard, Serious Rails Hosting
-- (866) 518-YARD (9273)



--~--~---------~--~----~------------~-------~--~----~
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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

surf

2007-Jan-31 22:00 UTC

head link

Re: Storing ActiveRecords in the Session

On Jan 31, 5:51 pm, Ezra Zygmuntowicz
<ezmob...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:> On Jan 31, 2007, at 12:28 PM, Robert Head wrote:
>
>
>
>
>
> > Tom Mornini wrote:
> >> On Jan 26, 2007, at 1:57 PM, Robert Head wrote:
>
> >>> Peter Ertl wrote:
> >>>> just store the primary key of the record...
that''s usually much
> >>>> better
>
> >>> Sure, but then I have to hit the DB *every time* I use it, no?
>
> >> No, it''s relatively easy to make sure the
''penalty'' is once per page
> >> that uses it.
>
> > OK, exactly.  So, what is the "relatively easy" way to make
sure the
> > object is only loaded once per page?
>
> > - Still perplexed
>
> > --
> > Posted viahttp://www.ruby-forum.com/.
>
>    def current_user
>      @current_user ||= session[:user_id] ? User.find_by_id(session
> [:user_id]) : nil
>    end
>
> This will cache the the user in @current_user so you can call
> current_user multiple times during a request and it will only hit the
> db once.
>

 This reminds me of something similar, suppose on sign up or in some
form the user has to fill in 20 or 30 fields and send them to the
server. The server validates them and creates a record on the
database. However, suppose that there is some complex logic that needs
to validate the form data beyond some simple stuff you could do
through javascript, perhaps you could do some sort of AJAX thing, but
the other possibility seems to be to store the form fields in the
session because the record may not get created on the database if
there is a problem, but you don''t want the user to have to fill the
fields all in again. I did it that way previously before I had done
much AJAX, but then I realized the session uses alot of space on the
file system.

--~--~---------~--~----~------------~-------~--~----~
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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Phlip

2007-Jan-31 22:29 UTC

head link

Re: Storing ActiveRecords in the Session

surf wrote:
> This reminds me of something similar, suppose on sign up or in some
> form the user has to fill in 20 or 30 fields and send them to the
> server. The server validates them and creates a record on the
> database. However, suppose that there is some complex logic that needs
> to validate the form data beyond some simple stuff you could do
> through javascript, perhaps you could do some sort of AJAX thing, but
> the other possibility seems to be to store the form fields in the
> session because the record may not get created on the database if
> there is a problem, but you don''t want the user to have to fill
the
> fields all in again. I did it that way previously before I had done
> much AJAX, but then I realized the session uses alot of space on the
> file system.
I would try this:

 - database table with a ''committed'' boolean
 - uncommitted records are disposable
 - committed records are transactable
 - build a Model out of the table with no validators
 - inherit a class, Q, from that Model & add validators
 - paint the form with the Model & submit it
 - to commit, copy the attributes into an instance of Q
 - set the committed bit, and try to save

I don''t know if each detail there would work, or cause problems. But in
general the point of OO is to abstract the thing that varies, so if the 
validators are the issue you should arrange to move them out of the way, 
instead of working around them. A user with a partly committed form should 
be able to return to it.

-- 
  Phlip
  http://www.greencheese.us/ZeekLand <-- NOT a blog!!!


--~--~---------~--~----~------------~-------~--~----~
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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Robert Head

2007-Feb-01 00:10 UTC

head link

Re: Storing ActiveRecords in the Session

Ezra Zygmuntowicz wrote:> 
>    def current_user
>      @current_user ||= session[:user_id] ? User.find_by_id(session
> [:user_id]) : nil
>    end
> 
> This will cache the the user in @current_user so you can call
> current_user multiple times during a request and it will only hit the
> db once.
> 
> -- Ezra Zygmuntowicz
I''ll try that again, but, IIRC, the last time I tried it, I was getting
marshaling problems when saving the object for some reason.

Thanks.

-- 
Posted via http://www.ruby-forum.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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Ezra Zygmuntowicz

2007-Feb-01 00:29 UTC

head link

Re: Storing ActiveRecords in the Session

On Jan 31, 2007, at 4:10 PM, Robert Head wrote:
>
> Ezra Zygmuntowicz wrote:
>>
>>    def current_user
>>      @current_user ||= session[:user_id] ? User.find_by_id(session
>> [:user_id]) : nil
>>    end
>>
>> This will cache the the user in @current_user so you can call
>> current_user multiple times during a request and it will only hit the
>> db once.
>>
>> -- Ezra Zygmuntowicz
>
> I''ll try that again, but, IIRC, the last time I tried it, I was  
> getting
> marshaling problems when saving the object for some reason.
>
> Thanks.
>
	Don''t save the whole object thats the entire point. Just save the  
objects id in the session. That method will use the id to do a db  
lookup and then cache the results.


-- Ezra Zygmuntowicz 
-- Lead Rails Evangelist
-- ez-NLltGlunAUd/unjJdyJNww@public.gmane.org
-- Engine Yard, Serious Rails Hosting
-- (866) 518-YARD (9273)



--~--~---------~--~----~------------~-------~--~----~
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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Robert Head

2007-Feb-01 13:14 UTC

head link

Re: Storing ActiveRecords in the Session

Ezra Zygmuntowicz wrote:
>   Don''t save the whole object thats the entire point. Just save
the
> objects id in the session. That method will use the id to do a db
> lookup and then cache the results.
To clarify, the question is what class your suggested code lives in.

When I created instance variables (where you are caching the object) in 
a model class, saving the record generated marshaling exceptions.

An example like your current_user method looks like it would probably 
live in a controller or helper and therefore not be saved and not create 
a problem.

Should I be able to drop ActiveRecord objects into instance variables in 
another ActiveRecord instance without getting marshaling problems?  I 
should test again, but that is contrary to my experience.

-- 
Posted via http://www.ruby-forum.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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

anibalrojas-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org

2007-Feb-01 13:35 UTC

head link

Re: Storing ActiveRecords in the Session

Take a look at  object_id_session plugin from Yurii Rashkovskii:

http://rashkovskii.com/articles/2007/1/2/object_id_session

--
Aníbal Rojas
http://www.rubycorner.com
http://www.hasmanydevelopers.com

On Jan 31, 8:29 pm, Ezra Zygmuntowicz
<ezmob...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:> On Jan 31, 2007, at 4:10 PM, Robert Head wrote:
>
>
>
>
>
> > Ezra Zygmuntowicz wrote:
>
> >>    def current_user
> >>      @current_user ||= session[:user_id] ? User.find_by_id(session
> >> [:user_id]) : nil
> >>    end
>
> >> This will cache the the user in @current_user so you can call
> >> current_user multiple times during a request and it will only hit
the
> >> db once.
>
> >> -- Ezra Zygmuntowicz
>
> > I''ll try that again, but, IIRC, the last time I tried it, I
was
> > getting
> > marshaling problems when saving the object for some reason.
>
> > Thanks.
>
>         Don''t save the whole object thats the entire point. Just
save the
> objects id in the session. That method will use the id to do a db
> lookup and then cache the results.
>
> -- Ezra Zygmuntowicz
> -- Lead Rails Evangelist
> -- e...-NLltGlunAUd/unjJdyJNww@public.gmane.org
> -- Engine Yard, Serious Rails Hosting
> -- (866) 518-YARD (9273)

--~--~---------~--~----~------------~-------~--~----~
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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Rails - Jan 2007 - Storing ActiveRecords in the Session

Storing ActiveRecords in the Session

Re: Storing ActiveRecords in the Session

Re: Storing ActiveRecords in the Session

Re: Storing ActiveRecords in the Session

Re: Storing ActiveRecords in the Session

Re: Storing ActiveRecords in the Session

Re: Storing ActiveRecords in the Session

Re: Storing ActiveRecords in the Session

Re: Storing ActiveRecords in the Session

Re: Storing ActiveRecords in the Session

Re: Storing ActiveRecords in the Session

Re: Storing ActiveRecords in the Session