Changeset 458 for elixir/trunk/CHANGES

Show
Ignore:
Timestamp:
09/17/09 13:54:19 (3 years ago)
Author:
ged
Message:

- Changed the pattern used by default to generate column names for (all)

ManyToMany relationships so that the meaning of bidirectional
self-referential relationships does not depend on the order of declaration
of each side (closes #69). See upgrade notes for details.

- Made M2MCOL_NAMEFORMAT accept a callable, so that more complex naming

generation can be used if so desired.

Files:
1 modified

Legend:

Unmodified
Added
Removed

  • elixir/trunk/CHANGES

    r448 r458  
    22 
    33Please see http://elixir.ematia.de/trac/wiki/Migrate06to07 for detailed 
    4 upgrade notes. 
     4upgrade notes. If you are upgrading an application with existing data from an 
     5earlier version of Elixir, you are VERY STRONGLY ADVISED to read them! 
    56 
    67New features: 
    … …  
    2021  ManyToMany table in a custom schema and not necessarily the same schema as 
    2122  the table of the "source" entity (patch from Diez B. Roggisch). 
    22 - Added a new "target_column" argument on ManyToOne relationships (ticket #26). 
    23   TODOC 
     23- Added a new "target_column" argument on ManyToOne relationships so that you 
     24  can target unique but non-primary key columns. At the moment, this only works 
     25  if the target column is declared before the ManyToOne (see ticket #26). 
    2426- Added new column_names argument to the acts_as_versioned extension, allowing 
    2527  to specify custom column names (inspired by a patch by Alex Bodnaru). 
    … …  
    4951 
    5052Bug fixes: 
     53- Changed the pattern used to generate column names for all ManyToMany 
     54  relationships so that the meaning of bidirectional 
     55  self-referential relationships does not depend on the order of declaration 
     56  of each side (closes #69). See upgrade notes for details. 
     57- Changed slightly the pattern used to generate the name of the table for 
     58  bidirectional self-referential ManyToMany relationships so that it doesn't 
     59  depend on the order of declaration of each side (closes #19). 
     60  See upgrade notes for details. 
    5161- default EntityCollection raise an exception instead of returning None when 
    5262  trying to resolve an inexisting Entity from outside of another entity (for 
    5363  example through EntityCollection.__getattr__ 
    54 - Changed slightly the algorithm to generate the name of the table for 
    55   bidirectional self-referential ManyToMany relationships so that it doesn't 
    56   depend on the order of declaration of each side (closes #19). If you are 
    57   upgrading an application with existing data from an earlier version of 
    58   Elixir, you are STRONGLY ADVISED to read the upgrade notes! 
    59   ================= 
    60   TEMPORARY NOTICE: 
    61   ================= 
    62   For now it is even worse: the table works but the relationship's meaning is 
    63   reversed. Will be fixed before 0.7 ships (see ticket #69). 
    64   ================= 
    6564- Fixed the case where you specify both "primaryjoin" and "colname" arguments 
    6665  (useless in this case, but harmless) on a ManyToOne relationship of an 
    … …  
    7271  secondaryjoin as not been specified manually. 
    7372- Added missing documentation for the "filter" argument on OneToMany 
    74   relationships 
     73  relationships. 
    7574- Fixed the act_as_list extension's move_to_bottom method to work on MySQL 
    7675  (closes #34). 
    7776- Fixed event methods not being called when they are defined on a parent class. 
    78   (introduced in r262). 
     77  (introduced in release 0.5.0). 
    7978- Added workaround for an odd mod_python behavior (class.__module__ returns a 
    8079  weird name which is not in sys.modules).