Session handling busted on Oracle

[Berger, Daniel]

> -----Original Message-----
> From: camping-list-bounces at rubyforge.org 
> [mailto:camping-list-bounces at rubyforge.org] On Behalf Of 
> Jonas Pfenniger
> Sent: Friday, October 05, 2007 9:54 AM
> To: camping-list at rubyforge.org
> Subject: Re: Session handling busted on Oracle
> 
> 
> Hi Daniel,
> 
> I think that I have corrected that last week changeset [226]. 
> The problem was that Session uses it's own kind of id 
> (hashid) and that by default, ActiveRecord uses an 
> incremental version.
> 
> See : http://code.whytheluckystiff.net/camping/changeset/226
> 
> Please tell me if I introduced any regression.

Doesn't work. Same error basically:

[2007-10-05 14:46:17] ERROR NoMethodError: undefined method `[]=' for
nil:NilClass
 
C:/ruby/lib/ruby/gems/1.8/gems/camping-1.5/lib/camping/session.rb:24:in
`[]='
 
C:/ruby/lib/ruby/gems/1.8/gems/camping-1.5/lib/camping/session.rb:129:in
`service'
        (eval):44:in `run'
 
C:/ruby/lib/ruby/gems/1.8/gems/camping-1.5/lib/camping/reloader.rb:117:i
n `run'
 
C:/ruby/lib/ruby/gems/1.8/gems/camping-1.5/lib/camping/webrick.rb:45:in
`service'
        C:/ruby/lib/ruby/1.8/webrick/httpserver.rb:104:in `service'
        C:/ruby/lib/ruby/1.8/webrick/httpserver.rb:65:in `run'
        C:/ruby/lib/ruby/1.8/webrick/server.rb:173:in `start_thread'
        C:/ruby/lib/ruby/1.8/webrick/server.rb:162:in `start'
        C:/ruby/lib/ruby/1.8/webrick/server.rb:162:in `start_thread'
        C:/ruby/lib/ruby/1.8/webrick/server.rb:95:in `start'
        C:/ruby/lib/ruby/1.8/webrick/server.rb:92:in `each'
        C:/ruby/lib/ruby/1.8/webrick/server.rb:92:in `start'
        C:/ruby/lib/ruby/1.8/webrick/server.rb:23:in `start'
        C:/ruby/lib/ruby/1.8/webrick/server.rb:82:in `start'
        C:/ruby/lib/ruby/gems/1.8/gems/camping-1.5/bin/camping:244
        C:/ruby/bin/camping:16:in `load'

Dan


This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly 
prohibited and may be unlawful.  If you have received this communication 
in error, please immediately notify the sender by reply e-mail and destroy 
all copies of the communication and any attachments.