Skip to Content
Last modified by Ravi Mendis on 2012/02/11 08:28
From version 152.1
edited by Ravi Mendis
on 2010/09/09 23:11
Change comment: There is no comment for this version
To version 153.1
edited by Ravi Mendis
on 2010/11/10 00:10
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -25,6 +25,8 @@
25 25  
26 26  If you're updating the state of EOs directly in the database using SQL from Scala Actors, you will subsequently need to refresh/refetch these EOs for the WebObjects application to see those changes.
27 27  
28 +You must also unlock attributes you update via SQL in order to prevent EOF optimistic locking exceptions.
29 +
28 28  == EOF Alternatives ==
29 29  
30 30  You may also manipulate the database from outside the EOF stack.
... ... @@ -37,6 +37,8 @@
37 37  
38 38  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. 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.
39 39  
42 +To generate a Squeryl schema from an EO model see [[WebObjects and Squeryl]]
43 +
40 40  === External Links ===
41 41  
42 42  WOWODC '10 Slides - [[http://www.wocommunity.org/wowodc10/slides/Scala+WO.pdf]]