I have used the ‘reverse
engineer’ option in the Entity-Modeller, that has created an Entity based
on my database view, and set its property to read-only [which is what I wanted].
When I verify the model, I get
an error saying View[etc] must have a primary key defined, so I guess I will
modify my view and create a ‘fictional’ primary key attribute...
I don’t know it feels like
I am not on the right track having to create a primary key in my database view.
From:
webobjects-dev-bounces+george=email@hidden
[mailto:webobjects-dev-bounces+george=email@hidden] On
Behalf Of George
Sent: Tuesday, 11 November 2008 1:22 p.m.
To: email@hidden
Subject: WebObjects binding to MYSQL Views
I have some reporting requirements that are experiencing
performance/load issues, when aggregating data using EO objects and
transversing all their relationships. To solve this I have created a
MYSQL view which ‘flattens’ the data structure and executes very
quickly, [and should go some way to fixing the performance issues].
I am struggling to figure out how to create and bind a
‘read-only’ entity in the eclipse Entity-Modeller perspective, to
my database VIEW. Is this possible [and where do I find the appropriate
documentation], OR do I have to use a raw rows query on the VIEW
directly? From a maintenance perspective I would rather use Entities than
raw row queries [that are buried in the code].
I use eclipse 3.3.2 running Wolips, using the WebObjects
Framework (non-wonder) 5.3.
Regards
George Wiles | Software
Development
TXT2GET | P +64 4 384 1438 | M +64 27 2758
143
Level 5, 75 Ghuznee Street, Wellington, New
Zealand
email@hidden|
www.txt2get.co.nz
No virus
found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.175 / Virus Database: 270.9.0/1779 - Release Date: 10/11/2008 7:53
a.m.