Hello, Again I've tried to use PO in several test cases and a third time I've failed.
While creating a workaround to the definition name/class name problem described in last mail, I discovered one more thing: First of all: database design related to foreign keys is another thing, but lead to this problem, described below. Find queries for related objects always based on the real database table field. The call to "where" method is simply loopthroughed, where the select aliases all field with there propertyName. Because of this, it's not possible, to separate definition and object class from domain layer, where data will be used. Changing field names for example would depend on a change within domain layer, where query was created. Again: is this a bug or a feature? Kind Regards Christian Michel Btw: None of my former questions is answered. -- Christian Michel Programmierung / Technik www.billiger-mietwagen.de ----------------------------- SilverTours GmbH Zweigstelle Köln Dompropst-Ketzer-Str. 1-9 50667 Köln HRB: 7144 (Amtsgericht Freiburg) Geschäftsführer: Christian Mahnke Tel.: (+49) 0221 272-408-80 Fax: (+49) 0221 272-408-29 -- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components
