Does the 'session' method do what you need?
http://rails.rubyonrails.org/classes/ActionController/SessionManagement/ClassMethods.html
On 3/24/06, Kyle Maxwell <[EMAIL PROTECTED]> wrote:
> Hi all,
> Rails tends to send the Set-cookie:_session_id... on every response,
> when session handling is e
Hi all,
Rails tends to send the Set-cookie:_session_id... on every response,
when session handling is enabled. Is there a way to only send that
header once (i.e. if the client doesnt send it in the request header)?
I have a web services client that will crash on getting redundant
cookies. Oh, an
My last response was to Rick's message, not Mark's. I'll blame gmail
for the confusion. :)
Mark's response looks to be correct.
On 3/23/06, Andrew Kaspick <[EMAIL PROTECTED]> wrote:
> Yes, I did that and works, just seems like a "hack" to an underlying
> issue. Currently the solutions you propo
Yes, I did that and works, just seems like a "hack" to an underlying
issue. Currently the solutions you proposed is what I have done, but
it took some time to figure it out.
On 3/23/06, Rick Olson <[EMAIL PROTECTED]> wrote:
> On 3/23/06, Andrew Kaspick <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
>
Andrew Kaspick wrote:
options = {:limit => 10}
logger.debug Division.find(1).teams.find(:all, options)
logger.debug Division.find(2).teams.find(:all, options)
logger.debug Division.find(3).teams.find(:all, options)
This produces the following sql in the order seen in the contro
On 3/23/06, Andrew Kaspick <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I came across what I believe is to be a bug in ActiveRecord with the
> latest revision of edge rails.
>
> Basically what the problem deals with is any passed options to a
> secondary find which are being modified internally when I b
Hello,
I came across what I believe is to be a bug in ActiveRecord with the
latest revision of edge rails.
Basically what the problem deals with is any passed options to a
secondary find which are being modified internally when I believe they
shouldn't be. Further explanation is easiest with cod
I've been bugged recently by the way table names are resolved for test fixtures.
A side-effect of the current method is that you have to name all of
your fixture accessors after the table, rather than after the class
name.
This means that things get a little less obvious for people using
set_table_
