Hi all,
I have just committed a chunk of work towards flattened relationships.
It is the first step, and consisted of the following:
Adding EntityResolver - this is now the main way to resolve between
ObjEntity/Names, Classes and DbEntities. lookupEntity in QueryEngine is
now deprecated, and should no longer be used. (There's still references
to it in the tests... what's the policy on removing tests to deprecated
functionality?)
Modifying all known uses of QueryEngine.lookupEntity to use
getEntityResolver.lookupObjEntity instead.
Adding set/getRoot to Query/AbstractQuery. This will become the basis
for the new means of creating Queries, and will replace
set/getObjEntityName (that's the next step - queries will be then
created by Class, or ObjEntity, or DbEntity, and only entity name if you
really want to)
Now only one ObjEntity in a Domain (and hence also a DataMap) may be
backed by a given Class (name). Nodes are handled implicitly by this (I
think). Unit test database structure had to be revised slightly to fit
this (Painting1, SubPainting, ArtistPaintingCounts, ROArtist and
ROPainting all needed their own DataObject classes).
I think that was all. Thanks Andrus for the guidance on this, my first
major commit.
Craig
This archive was generated by hypermail 2.0.0 : Tue Nov 12 2002 - 21:24:21 EST