Changeset 363 for elixir/trunk/CHANGES

Show
Ignore:
Timestamp:
07/14/08 21:51:36 (6 years ago)
Author:
ged
Message:

- Default "target entity resolving code" changed slightly. It now uses a global

collection keyed on the entity name. This means that entities can refer to
other entities in a different module simply with the target entity name
instead of its full path. The full path is only required when there is an
ambiguity (ie when there are two classes with the same name in two different
modules). Closes #9.

- minor cleanup of some test files
- changelog some earlier changes

Files:
1 modified

Legend:

Unmodified
Added
Removed
  • elixir/trunk/CHANGES

    r362 r363  
    99  polymorphic or not). Concrete polymorphic inheritance requires SQLalchemy 
    1010  0.4.5 or later. 
     11- Moved the entity to string mapping and resolving code to the (newly created) 
     12  EntityCollection class (which stores lists of entities). This allows one to 
     13  provide a custom mapping method if needed. The default class also overrides 
     14  the __getattr__ method, providing and handy way to get at your entities. 
     15  See source:elixir/trunk/tests/test_collections.py#L58 
    1116- Added new "identity" option which can be used to set a custom polymorphic 
    1217  identity for an entity. It also accepts a callable so that you can generate 
     
    3035 
    3136Changes: 
     37- Default "target entity resolving code" changed slightly. It now uses a global 
     38  collection keyed on the entity name. This means that entities can refer to 
     39  other entities in a different module simply with the target entity name 
     40  instead of its full path. The full path is only required when there is an 
     41  ambiguity (ie when there are two classes with the same name in two different 
     42  modules). Closes #9. 
    3243- Added support for SQLAlchemy 0.5, and dropped support for version 0.3 and 
    3344  earlier.