IanBlackburn wrote:
Otis wrote:
Entitycollection classes are always overwritten. The 2-class scenario has 2 classes per entity: one for your code and one which is generated, though not a pair per collection.
Thanks Otis,
So is the "Custom User Code" region in these class in preperation for the changes you making in the next release where these regions will be untouched be the code generator?
Ian
No, that region is for include code via a template you bind yourself to the templateID stated in the region in the actual template, for example Custom_EntityAdapter will be the ID for the include template included in the custom user code region in an adapter's entity class.
The region is not properly named and will be renamed.
In the upgrade now in development, a new feature will be added where you can add code to sections which have the same name as a TDL statement in the template, at that same spot. That way, your code will be preserved and will be merged with the genreated code.
The only problem with that is that code in a given scope (for example inside a forloop in a method) also has to be merged in the same scope in the generated code . What I want is that certain methods can be extended in code by you for example the init class methods, updateentity method etc. without the need for inheritance.