Reordering mappings from domain in xml resulting in StackOverflowException
--
Key: CAY-743
URL: https://issues.apache.org/cayenne/browse/CAY-743
Project: Cayenne
Issue T
Just for curiosity I added Cayenne to http://www.sourcekibitzer.org a
few days ago. I figured it may not help, but it couldn't hurt.
You can access reports at URL: http://www.sourcekibitzer.org/
index.php?option=com_skproject&task=view&projectid=cayenne
Personally, I think most of the repor
Currently, I've hacked up the 1.2 Modeler to support my own client
needs. I added a Description field to DbEntity and DbAttribute for
comments. I also ended up needing a few other fields attached to
ObjEntity, ObjRelationship, DbEntity, and DbRelationship, so my
personal preference would be a
My thinking on design would be to keep it a simple (80/20 rule
solution), in which I think a simple comment attribute to the mapping
XML elements. In an XML attribute we have to take care encoding the
value.
With a simple optional attribute, I would think it would be a pretty
safe bet that there
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
Andrus Adamchik wrote:
> I guess the term "comment" is too narrow and misleading here. I was
> thinking more of a CAY-400 approach:
>
> https://issues.apache.org/cayenne/browse/CAY-400
>
> I.e. a list of key/value pairs rather than a single comment.
While technically comments could be represente
Andrus Adamchik wrote:
> Hi Dirk,
>
> 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 b
Read the entire post.
Of course I did :).
The discussion is about how to avoid
loading/parsing of all that stuff in runtime.
I just thought that skipping XML nodes is not a performance overhead,
but transforming those nodes into objects would be.
At least with the few fast XML parsers I used
Read the entire post. The discussion is about how to avoid loading/
parsing of all that stuff in runtime.
Andrus
On Jan 31, 2007, at 4:15 PM, Ahmed Mohombe wrote:
I also had performance concerns.
Why should performance be a problem in this case?
Comments are not required at runtime, just a
I also had performance concerns.
Why should performance be a problem in this case?
Comments are not required at runtime, just at "design/develop" time.
Ahmed.
Hi Dirk,
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
I guess the term "comment" is too narrow and misleading here.
Maybe, but what I'm missing from Cayenne(+modeler) are really "comments"
in the simple form, not annotations or other fancy things: just comments.
Depending on the working procedure, to be able to propagate them(or override).
E.g.:
> Hi All,
Hi,
> We use Cayenne day in day out for a lot of our work, and the Cayenne
> Modeler has a pretty central place in maintaining the database design,
> and hence the application design.
Documentation for the database model has been an issue that I was
interested in since the EOF days.
>
I guess the term "comment" is too narrow and misleading here. I was
thinking more of a CAY-400 approach:
https://issues.apache.org/cayenne/browse/CAY-400
I.e. a list of key/value pairs rather than a single comment.
Andrus
On Jan 31, 2007, at 3:17 PM, Ahmed Mohombe wrote:
I can better comme
I can better comment on specifics if we decide on a visual solution
first. Since comments can be added to almost any mapping element
-[Obj|Db] [Entity|Attribute|Relationship] Query (?), my first thought is
to add an info button (same as the one used on relationships panels) to
the rest of the m
Excellent! I am glad to see you stepping in to do that. We promised
this feature so many times that I blush every time somebody asks for
it again :-)
As for the Modeler architecture, it is a bit eclectic, as we tried a
number of approaches over time, not always fully cleaning up the
depre
Hi All,
We use Cayenne day in day out for a lot of our work, and the Cayenne
Modeler has a pretty central place in maintaining the database design,
and hence the application design.
Being able to have comments associated with DbEntity attributes and
relationships would be an extremely useful fea
17 matches
Mail list logo
