Changes for page WebObjects and Squeryl

Last modified by Ravi Mendis on 2011/04/01 11:14

From version 85.1
edited by Ravi Mendis
on 2010/11/10 04:54
Change comment: There is no comment for this version
To version 84.1
edited by Ravi Mendis
on 2010/11/10 06:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,6 +1,6 @@
1 1  = Squeryl ~= //SQL-like// DSL for Scala =
2 2  
3 -Advantages of Squeryl over EOF:
3 +Advantages of [[Squeryl>>http://squeryl.org/]] over EOF:
4 4  
5 5  * Concurrent
6 6  ** Spawns multiple database connections
... ... @@ -10,19 +10,19 @@
10 10  * Strongly-typed
11 11  ** Better suited for database/business "logic".
12 12   E.g: Exploits the compiler and IDE to catch exceptions at compile time rather than at run-time.
13 -* Uses Scala (functional) collection classes
13 +* Uses Scala collection classes
14 14  
15 15  = Migrating EOF -> Squeryl =
16 16  
17 -In keeping with the strongly-typed philosophy of Scala, Squeryl has no dynamic component like EOF (i.e an EO model file).
17 +In contrast to EOF Squeryl maintains its ORM information programmatically - in the classes itself and collectively in a [[schema>>http://squeryl.org/schema-definition.html]]. In keeping with the strongly-typed philosophy of Scala, Squeryl has no dynamic component like EOF (i.e an EO model file).
18 18  
19 -EOF has the ability to generate classes in Java (and in Objective-C prior to WebObjects 4.5) as enforcing type has become customary in enterprise environments. We may exploit this feature of EOF to generate a Squeryl schema.
19 +EOF has the ability to generate classes in Java (and in Objective-C prior to WebObjects 4.5) because enforcing type has become customary in enterprise environments. We may exploit this feature of EOF to generate a Squeryl schema from an EO model.
20 20  
21 21  === Preparing your EO model ===
22 22  
23 -* Make sure **all** EO entities have a class name (including abstract many-To-many "join" tables). There's no support for entities marked as ##EOGenericRecord##.
23 +* Make sure **all** EO entities have a class name (including abstract many-To-many "join" tables). FYI: There can be no support for entities classified as ##EOGenericRecord##.
24 24  * Mark the abstract many-To-Many join entities as ##Abstract##.
25 -* (Temporary) Ensure all the model entities are in the same package. i.e ##model## <-> ##package## corresponds 1-to-1.
25 +* (Temporary) Ensure all the model entities are in the same package. i.e the package is exclusive to the model.
26 26  
27 27  === Generating the Squeryl Schema ===
28 28  
... ... @@ -38,3 +38,9 @@
38 38  Any custom business "logic" will have to be manually re-written in Scala
39 39  
40 40  {{/note}}
41 +
42 +== Differences Between a Squeryl Schema and EOF Classes ==
43 +
44 +* Optional attributes (i.e those that ##allowsNull##) are typed as ##OptionT##
45 +* To one relationships that are not mandatory (i.e optional relationships) are also typed as ##OptionT##
46 +* To many relationships are represented as a Squeryl iterable (collection class) as opposed to a ##NSArray##.