Comment 2 for bug 581982

Revision history for this message
Chris Tusa (chris-tusa) wrote :

Resolved issue with comment #1 by improving creation of record by pre-creating caller id and expiration values in advance of the Session.new call. Issue now found when logging out as shown below with a failed DELETE statement. More than likely this is a result of the $session variable in lib/tglogin.rb not knowing its own ID due to no refresh. Again. this issue ONLY occurs during the first login.

/data/devel/lang/jruby-1.5.0/lib/ruby/gems/1.8/gems/sequel-3.12.0/lib/sequel/model/base.rb:863:in `_delete': Attempt to delete object did not result in a single row modification (Rows Deleted: 0, SQL: DELETE FROM "SESSIONS" WHERE ("ID" IS NULL)) (Sequel::NoExistingObject)
 from /data/devel/lang/jruby-1.5.0/lib/ruby/gems/1.8/gems/sequel-3.12.0/lib/sequel/model/base.rb:624:in `delete'
 from /data/devel/lang/jruby-1.5.0/lib/ruby/gems/1.8/gems/sequel-3.12.0/lib/sequel/model/base.rb:886:in `_destroy_delete'
 from /data/devel/lang/jruby-1.5.0/lib/ruby/gems/1.8/gems/sequel-3.12.0/lib/sequel/model/base.rb:877:in `_destroy'
 from /data/devel/lang/jruby-1.5.0/lib/ruby/gems/1.8/gems/sequel-3.12.0/lib/sequel/model/base.rb:635:in `destroy'
 from /data/devel/lang/jruby-1.5.0/lib/ruby/gems/1.8/gems/sequel-3.12.0/lib/sequel/model/base.rb:1006:in `checked_transaction'
 from /data/devel/lang/jruby-1.5.0/lib/ruby/gems/1.8/gems/sequel-3.12.0/lib/sequel/database/query.rb:167:in `_transaction'
 from /data/devel/lang/jruby-1.5.0/lib/ruby/gems/1.8/gems/sequel-3.12.0/lib/sequel/database/query.rb:153:in `transaction'
 from /data/devel/lang/jruby-1.5.0/lib/ruby/gems/1.8/gems/sequel-3.12.0/lib/sequel/connection_pool/threaded.rb:84:in `hold'
  ... 7 levels...
 from ./lib/tgio/input.rb:342:in `menuprompt'
 from ./lib/controllers/main.rb:62:in `menu'
 from ./tg.rb:170