Skip to Content
Last modified by Ravi Mendis on 2012/02/11 08:28
From version 142.1
edited by Ravi Mendis
on 2010/04/05 21:18
Change comment: There is no comment for this version
To version 143.1
edited by Ravi Mendis
on 2010/03/24 23:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -12,7 +12,7 @@
12 12  
13 13  EOF being notoriously single-threaded, is incredibly unsuitable for use with Scala Actors:
14 14  
15 -* EOs are mutable objects and as such they cannot be passed safely to Scala Actors
15 +* EOs are mutable objects and as such they cannot be passed safely into Scala Actors
16 16  * Fetching and updating EOs from within Scala Actors can cause [[deadlocks>>http://en.wikipedia.org/wiki/Deadlock]] with the WebObjects application
17 17  
18 18  Instead you can still use EOF but in a limited fashion - only to execute SQL.
... ... @@ -31,8 +31,7 @@
31 31  
32 32  === Squeryl ===
33 33  
34 -[[Squeryl>>http://max-l.github.com/Squeryl/index.html]] is a strongly typed and declarative [[Domain-specific language>>http://en.wikipedia.org/wiki/Domain-specific_language]] for manipulating database objects from within the Scala language.{{quote}}{{/quote}}
35 -
34 +[[Squeryl>>http://max-l.github.com/Squeryl/index.html]] is a Scala internal [[Domain-specific language>>http://en.wikipedia.org/wiki/Domain-specific_language]] for database access (via SQL).
36 36  You may update the database from Scala Actors using Squeryl instead of using EOF. The advantage here is that you may access the database concurrently avoiding the single-threaded EOF bottleneck in your application.
37 37  
38 38  However the same caveat applies - you will need to refresh EOs in the EOF stack for the WebObjects application to reflect the changes made by Squeryl.