Prev | Current Page 579 | Next

L. McColl-Sylvester and F. Ponticelli

"Professional haXe and Neko"

* from Lookup l inner join
Chapters c on l.int_chapter = c.int_id where l.int_author = ???
+ a, true );
}
}
(continued)
301
Chapter 11: Performing Server-Side Trickery
So, what do these two classes do? Well, first they map the specific record object type and class to the
underlying Manager class functionality. One could supply a T value, which represents a template,
meaning that you could supply the values for the type and class when instantiating the class. However,
seeing as the data queries are hard coded, the associated data type will be unlikely to change.
Once the classes are instantiated and the underlying functionality is initialized, each class specifies a
reference to the other class in a static variable. Now, this took some figuring out when we first performed
a many - to - many query using the SPOD system, though it now seems to work very well. It appears that,
when the make method is called following a query for the type associated with the Manager object, the
aforementioned type is then bound to any queries made using the Manager methods.


Pages:
567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591