James-Vincent Brady
2004-08-06 05:09:03 UTC
Hi All,
I have just discovered that CMR is not a good idea if relationships lead to very large 'N' sides of 1:N relationships. However, I can find no way to disable them in middlegen. Is there one (other than the primitive trick of removing the constraints in a copy of the database and then generating)?
Also, I have spent some time improving on the application that Middlegen generates, via repeditive editing and just haven't had the time to look into how easy it would be change the Velocity scripts. It probably would have saved me time in the end but the testing seems a hassle. I'm wondering whether someone with time and a better knowledge of velocity (and perhaps with an eye to something marketable at the end of the line) is interested in examples of the following:
1. Automatic audit trail field addition (and concurrent update checking) ;
2. Selectable paged, lists using DISPLAYTAG;
3. Links from view function to related records (in new browser instance);
4. Error messaging - marking error fields;
5. Delete with confirmation (and Oh my God! restore functionality);
6. Copy function;
7. ... still being developed editing with authorisation.
It was tedious to develop but well worth it at the end. If somebody wants good examples and would give me a copy of the velocity at the end I would really appreciate it.
Jim Brady
--
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
I have just discovered that CMR is not a good idea if relationships lead to very large 'N' sides of 1:N relationships. However, I can find no way to disable them in middlegen. Is there one (other than the primitive trick of removing the constraints in a copy of the database and then generating)?
Also, I have spent some time improving on the application that Middlegen generates, via repeditive editing and just haven't had the time to look into how easy it would be change the Velocity scripts. It probably would have saved me time in the end but the testing seems a hassle. I'm wondering whether someone with time and a better knowledge of velocity (and perhaps with an eye to something marketable at the end of the line) is interested in examples of the following:
1. Automatic audit trail field addition (and concurrent update checking) ;
2. Selectable paged, lists using DISPLAYTAG;
3. Links from view function to related records (in new browser instance);
4. Error messaging - marking error fields;
5. Delete with confirmation (and Oh my God! restore functionality);
6. Copy function;
7. ... still being developed editing with authorisation.
It was tedious to develop but well worth it at the end. If somebody wants good examples and would give me a copy of the velocity at the end I would really appreciate it.
Jim Brady
--
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.