Home/ Questions/Q 7595419
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-30T21:40:07+00:00

Updated Question After some further debugging I’ve updated this question to be more accurate

  • 0

Updated Question After some further debugging I’ve updated this question to be more accurate on the actual problem.

I have a trait I’ve defined to do a basic security check but every time I want to run a DB query it throws a Cannot operate on a closed connection!!! error.

Code below:

trait SecureAPI {
  self:Controller =>

  @Before
  def checkKey(key:String)
    models.Account.getByKey(key) match {
      case account:Account  =>  {
        renderArgs += "account" -> accountId
        Continue
      }
      case _  =>  Forbidden("Key is not authorized.")
    }
}

The getByKey throws the DB error. In my controllers, I’m adding Squeryl as a trait, but how would I apply that in another trait so I can continue to run queries? Or am I just not approaching this properly? Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I got deeper into different readings and credit for this one goes to this post here: http://www.alvarocarrasco.com/2010/12/i-have-settled-on-new-platform-for.html

    I had to use Squeryl to bind the session to the current thread. So to make the above code work, I had to add in SessionFactory

    @Before
def checkKey(key:String)
  SessionFactory.newSession.bindToCurrentThread // added this here
  models.Account....

    Everything now queries, just need to work out a few bugs. I’ll update the answer if I discover any more caveats.

    • 0