Herbie van Tetering
Joined: 2008/01/08
Messages: 4
Location: Herbie van Tetering
Offline
|
|
|
|
Dear Sir,
I am developing an application, online company intranet, using the DB Visual Architect. With regards to the application, there are some alternatives that can be chosen to handle client-server technology implementation.
1) use our own persistency and data control layer (only java/php)
2) generate persistency code from visual paradigm (all languages)
3) generate only data definition with visual paradigm (only to sql)
4) use transformation layers between generated code (to/from java/php)
With regards to the persistency layer, in the persistency layer I have developed, I can join tables in several different ways, either from intermediate object selection results or from predefined joins between all objects in the database. These joins can be constrained by selections on objects which are a member of the joined group.
i.e.
[Teacher]0..*----0..*[Student]
join(Teacher, Student);
Teacher.setName("henry");
SelectJoined();
The result of this functionality in our persistency layer is that we can immediately choose subsets of those joins. With regards to this topic, I had some questions about the general persistency layer offered, in the different languages, by visual paradigm.
1) are there joined objects from multiple tables in the persistency layer?
2) where are the persistency layer and database functions documented?
3) are persistency layer functions triggered in activities or interactions?
4) how important is roadmap for development of the persistency layer?
Thank you.
|
|
|
|
