Changes for page WebObjects and Squeryl

Summary

• Page properties (1 modified, 0 added, 0 removed)

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
...	...	@@ -14,7 +14,7 @@
14	14
15	15	= Migrating EOF -> Squeryl =
16	16
17		-In contrast to EOF Squeryl maintains its ORM information programmatically - in the classes itself and collectively in a ##schema##. 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	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.
20	20
...	...	@@ -41,6 +41,6 @@
41	41
42	42	== Differences Between a Squeryl Schema and EOF Classes ==
43	43
44		-* Optional attributes (i.e those that ##allowsNull##) are typed as ##Option[[T]]##
45		-* Relationships that are not mandatory (i.e optional relationships) are also typed as ##Option[[T]]##
46		-* ToMany relationships are represented as a Squeryl iterable (collection class) as opposed to an ##NSArray##.
	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##.