Project

General

Profile

Actions
Copy link

Bug #2121

closed

The SQueryl implementation is not thread safe

Added by Nicolas CHARLES about 13 years ago. Updated about 13 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Nicolas CHARLES
Category:
Architecture - Code maintenance
Target version:
2.3.5
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

The way we use Squeryl is not valid, for the session are not rightly managed
We need to correct that, or thread-related bug might arise

Actions
Copy link
 #1

Updated by Nicolas CHARLES about 13 years ago

  • Status changed from In progress to Pending technical review
  • % Done changed from 0 to 100
Actions
Copy link
 #2

Updated by François ARMAND about 13 years ago

  • Status changed from Pending technical review to 10

To be more precise: as we don't want to limit Rudder to use only one Database / connection, we are not able to use Squeryl provided implementation of Session management, which is threadsafe.

So we have to use our own, which is more or less a copy/paste of squeryl one, extended to multiple connection.

The provided code seems ok.

Actions
Copy link
 #3

Updated by Jonathan CLARKE about 13 years ago

  • Status changed from 10 to Released
Actions
Copy link

Also available in: Atom PDF