Hello.
An extra file like that will probably make refactoring and keeping
things in sync more complicated. My app have millions of cayenne
objects laying around (will be better with 3.0), each with a HashMap,
so those Strings with documentation will take minimal - if not zero -
space and cpu. This will of course depend on the nature of your project.
Good luck Malcolm, this will be a great cayenne feature!
- Tore.
On Jan 31, 2007, at 15:06, Andrus Adamchik wrote:
> I also had performance concerns. So maybe store all that bulky
> optional metadata (be it just comments or some arbitrary key value
> pairs) in a separate properties file sitting next to the project
> descriptor (cayenne.properties?). Each property name will be
> prefixed with a location of the property-owning node in the project
> tree. E.g.:
>
> map:mymap1.dbentity:myentity1.abc.comment = ABC...
> map:mymap2.objentity:myentity2.abc.comment = XYZ...
>
> ... or something. Properties can be loaded lazily on first access
> and CayenneModeler would take care of building the proper keys.
This archive was generated by hypermail 2.0.0 : Wed Jan 31 2007 - 13:33:04 EST