root / elixir / trunk / CHANGES @ 327

0.6.0

New features:
- Added two new methods on the base entity: from_dict and to_dict, which can
  be used to create (or output) a whole hierarchy of instances from (to) a
  simple JSON-like dictionary notation (patch from Paul Johnston,
  closes ticket #40).
- Added experimental (!) support for concrete table inheritance (both 
  polymorphic or not). Concrete polymorphic inheritance requires SQLalchemy
  0.4.5 or later.
- Added new "identity" option which can be used to set a custom polymorphic
  identity for an entity. It also accepts a callable so that you can generate
  the identity name automatically from the class itself.

Bug fixes:
- Fixed multi-table inheritance when using a non default schema (closes #38)
- Fixed ManyToOne relationships using 'key' kwarg in their column_kwargs
  (patch by Jason R. Coombs) 
- Fixed inheritance with autoloaded entities: when using autoload, we 
  shouldn't try to add columns to the table (closes tickets #41 and #43).
- Fixed ColumnProperty to work with latest version of SQLAlchemy (O.4.5 and
  later)

Misc:
- Added AUTHORS list. If you are missing from this list, don't hesitate to
  contact me.

0.5.2 - 2008-03-28

New features:
- Added an optional `check_concurrency` keyword argument to the versioning 
  extension, supporting the usage of SQLAlchemy's built-in optimistic 
  concurrency check.

Changes:
- Made Elixir python 2.3 compatible again (based on patches from 
  Jason R. Coombs)

Bug fixes:
- Fixed act_as_list extension to work with DBMS that require subselects to be
  aliased (patch by Alice McGregor)
- Fixed the versioning extension so that the history table is updated within
  the current transaction (patch from and closes ticket #35).

0.5.1 - 2008-02-07

New features:
- Added a new elixir plugin for managing entities as (ordered) lists.
- Added a `column_format` keyword argument to `ManyToMany` which can be used 
  to specify an alternate format string for column names in the mapping table.
- Added support for custom base classes which inherit from another class (ie
  not directly from object).
- Added an alternate (nicer) syntax to define synonym properties.  This syntax
  has a more limited scope, except that it can refer to properties defined in 
  a parent entity. This is based on a patch from Alexandre da Silva.

Changes:
- Added check so that using an inexisting column in an order_by or other
  column-name based argument raises an exception.
- The polymorphic_identity kwarg in using_mapper_options is not overriden
  anymore by the one generated by Elixir (patch from Ben Bangert).
- Moved the format of the multi-table inheritance column to a constant in 
  options (so that it can be changed globally).
- The foreign key constraint of the column in a multi-table inheritance is
  configured with a cascade rule.

Bug fixes:
- A child entity doesn't inherit anymore its parent entity statements (such as
  options) if it doesn't use any statement itself.
- Made inheritance work for custom base classes (closes #25).
- Fixed the inverse relationship matching when the inverse relationship is 
  defined in a parent Entity (thanks to Alexandre da Silva).
- Fixed bug in setup_entities (it always used the global entity list and not
  the list given as argument).
- Fixed the versioning extension not appropriately handling versioned
  entities with onupdate events (patch from Remi Jolin, closes #29).
- Fixed videostore example (patch from Jason R. Coombs, closes #31).

0.5.0 - 2007-12-08

Please see http://elixir.ematia.de/trac/wiki/Migrate04to05 for detailed 
upgrade notes.

New features:
- Added set method on base Entity (set attributes using kwargs)

Changes:
- Autosetup defaults to False ! (please look at those upgrade notes!)
- Polymorphic defaults to True (inheritance is polymorphic by default).
- Removed one of the autosetup triggers altogether: there is no "fake" mapper
  registered in SQLAlchemy's mapper_registry anymore, so if you try to
  access the class mapper directly (not through the 'mapper' attribute on
  the class), before the setup phase happens, it won't work. This was done
  because of a change in SQLAlchemy trunk (future SA 0.4.2) which broke that
  piece of code (and prevented to use autosetup at all). Since that code 
  was a hack in the first place, instead of doing some even uglier hackery, 
  I got rid of it altogether.
- Moved some format strings to constants in options, so that one can change
  them if he wants to.
- Allow overriding primary_key columns on autoloaded entities (closes tickets
  #20 and #22)
- Columns created by ManyToOne relationships can now optionally (through 
  column_kwargs) *not* create an index (ie it's not harcoded anymore).
  Suggestion by Jason R. Coombs.

Bug fixes:
- Fixed a nasty bug which prevented inheritance to work correctly when using 
  the attribute syntax in many cases.
- Fixed associable extension to work with SQLAlchemy trunk (future 0.4.2).
- Fixed an incompatibility with zope.interfaces.
- Tweaked the initialization sequence again (in fact revert an older change)
  which prevented to reuse class properties of one class in other (subsequent)
  classes.
- Fixed our tests to work with SA trunk (future 0.4.2) (unicode data + use of 
  deprecated attributes)

0.4.0 - 2007-10-29

Please see http://elixir.ematia.de/trac/wiki/Migrate03to04 for detailed 
upgrade notes.

New features:
- Implemented a new syntax to declare fields and relationships, much closer to
  what is found in other Python ORM's. The with_fields syntax is now
  deprecated in favor of a that new syntax. The old statement based (has_field 
  et al.) syntax is still available though (and will remain so for quite some
  time). This was done with help from a patch by Adam Gomaa.
- Implemented polymorphic single-table inheritance as well as polymorphic and
  non-polymorphic multi-table (aka joined table) inheritance.
- Added ext sub-package for additional Elixir statements.
- Added associable extension for generating polymorphic associations with 
  Elixir statements.
- Added versioning extension to keep track to all changes to your entities by
  storing them in a secondary table.
- Added encryption extenstion to encrypt/decrypt some fields data on the fly
  when writing to/reading from the database.
- Added support for synonym properties.
- Added shortcut syntax to define column_properties.
- Added a .query attribute on all entities. The old .query() syntax is still
  available.
- Added support to add any SQLAlchemy property on your mapper, through the
  GenericProperty class (as well as the has_property statement). These can
  work even if they rely on the entity columns (an thus need them to be 
  defined before the property can be declared). See tests/test_properties.py
  for examples.
- Added support for "manual session management" (ie you can now define an 
  entity with "using_options(session=None)" and it won't use any
  SessionContext extension, nor receive the "query" attribute.
- Made the statement system more powerfull.

Changes:
- The setup time was changed. That is the table and mapper are not created as
  soon as the class is defined, but rather when first used, or when explicitly
  calling the setup function (recommended). This also allowed us to reorder
  the setup process and allows, among others to use a ManyToOne-generated
  column as a primary key, to use unique constraints on those columns, to
  order by those columns and so on...
- Made Elixir work with both SQLAlchemy 0.4 and 0.3.10 (with help from a patch
  by Ants Aasma).
- Moved away from assign_mapper, now all assign_mapper-provided methods are on
  the Entity class. Now, if people don't like them, they have the option to
  simply provide another base class.
- Default objectstore is now a ScopedSession when working on SQLAlchemy 0.4. 
  It means that it's not wrapped in an Objectstore object at all. This means, 
  that depending on the version of SA you are using, you'll get a slightly 
  different behavior.
- Relationships to other classes can now also be defined using the classes
  themselves in addition to the class namees. Obviously, this doesn't work for
  forward references.
- Classes defined inside a function can now have relationships to each other.
- Added default __init__ method on entities so that subclasses can override it
  and still have the "set attribute by keyword" behavior by calling super()
- Added "through" and "via" keyword arguments on relationships and has_field
  statement, to proxy values through relationships (uses association_proxy)
- Made EntityMeta public, so that people can actually define their own base 
  class.
- Changed the order of relationship kwargs processing so that computed kwargs
  can be overridden by kwargs manually passed to the statement. This should
  only be used if you know what you are doing.
- Added onupdate kwarg to BelongsTo relationships for consistency with the
  ondelete kwarg
- Added ondelete and onupdate kwargs for use with has_and_belongs_to_many
  to apply on delete clauses to foreign key constraints on the m2m table.
- Columns of the intermediary table of an has_and_belongs_to_many relationship
  are now marked as primary keys.
- Reworked how entities look for primary keys on related entities. This
  enables one "normal" entity (fully defined in Elixir) to refer to an entity
  which is autoloaded.
- Added translation (from column name to column object) of the primary_key 
  mapper option so that it can actually be used. This allows to have entities
  without any primary key defined at the table level.
- Added the possibility to give a custom name for ManyToOne constraints
  (patch from and closes ticket #16)
- Dropped support for the old threadlocal SA extension (which doesn't even exist
  anymore in SA 0.4)

Bug fixes:
- Reworked/cleaned tests so that they don't leak stuff to other tests (both at
  the method level and module level) anymore. Uses nosetest's module level 
  fixture.
- Fixed relationships to entities whose primary_key field has been defined
  with a "key" argument (based on a patch by Paul Johnston).
- Fixed some buggy tests.
- Fixed relationships to tables using a schema (patch by Neil Blakey-Milner)
- Made inverse relationships use backrefs. This fixes the "bidirectional
  coherency" problem some people had before doing a flush. (based on a patch 
  from Remi Jolin).

0.3.0 - 2007-03-27
- Made the provided metadata not threadlocal. This could break things for you
  in some rare case. Please see the (newly created) FAQ file for details about
  this.
- Added support for autoloading/reflecting databases with
  has_and_belongs_to_many relationships. The tablename argument is now
  optional, but still recommended, otherwise you'll have to use the same exact
  name for your intermediary table than the one generated. You also _have to_
  specify at least one of either local_side or remote_side argument.
- Added support for the "version_id_col" option on entities. This option adds 
  a column to the table which will be used to prevent concurrent modifications
  on any row of the entity's table (i.e. it will raise an error if it happens).
- Made the colname argument optional for belongs_to relationships in
  autoloaded entities. It is only required to specify it if you have several
  belongs_to relationships between two entities/tables.
- Applied patch from "Wavy" so that columns of a table are in the same order
  as they were declared (this only works for the has_field statement).
- Applied patch from Isaac Csandl to add an "ondelete" argument to
  belongs_to relationships. The content of that argument is forwarded to the
  foreign key constraint.
- Foreign key names generated by belongs_to relationships use column names 
  instead of relation names in case we have a relation with the same name
  defined in several entities inheriting from the same entity using single-
  table inheritance (and we set a custom column name in one of them to avoid
  a column-name conflict).
- Using invalid options on entities will now raise an exception
- Added __version__
- Use an explicit metaclass for entities, so that people can define their own
  base class.
- Changed the approach to reflecting/autoloading belongs_to relationships.
  This shouldn't change anything to how it's used but allowed me to factor
  some code with has_and_belongs_to_many relationships.
- The tablename option can now be given a callable so that people can provide
  their own function to get the table name for an entity. The tablename option
  can now also be set globally (using the options_defaults dictionary). Of
  course, this only makes sense for the callable usecase.

- Fixed bug preventing having entities without any statement.
- Fixed documentation for belongs_to relationships (the arguemnt is "required",
  not "nullable").
- Fixed typo which broke the use_alter argument on belongs_to relationships.
- Fixed inheritance unit test to pass SQLAlchemy type check on relations
  (introduced in SA 0.3.6)
- Fixed wrong field length in autoload test (it was not noticeable with sqlite).
- Actually make the code python 2.3 compatible (Robin's patch was based on
  0.1.0 while I had introduced more decorators in the trunk in the mean time).

- Made some PEP8 tweaks in many places. Used the pep8 script provided with 
  Cheesecake.
- Some cleanup/useless code removal

0.2.0 - 2007-02-28
- Applied patch from Robin Munn to make the code python 2.3 compatible
- Per a suggestion on the mailing list, look at the calling stack frame to
  ensure that we apply statements to the proper class.  We now attach the
  statement list to the class itself, rather than attaching it to a global
  list that is neither threadsafe, nor safe when doing nested class 
  definition.  Also added a test to validate that this works.
- implemented singletable non-polymorphic inheritance
- added support to pass non-keyword arguments to tables. You just pass
  them to the using_table_options statement and they will be forwarded to the
  table along with the keyword arguments. This can be used to set table 
  constraints.
- added support for deferred columns (use the "deferred" keyword argument on
  fields)
- added a "required" keyword argument on fields and BelongsTo
  relationships. This is the opposite of the "nullable" SA argument.
- added a "column_kwargs" keyword argument to BelongsTo relationships 
  to forward any keyword argument directly to the SA Column.
- added support for the use_alter and constraint_kwargs kwargs on BelongsTo
  relationships (forwarded to SA ForeignKeyConstraint).
    -> removed the systematic use_alter on BelongsTo relations since it
       can now be specified only when needed.
    -> removed it from HasAndBelongsToMany relations, since I think a
       circular foreign key dependency can't happen with those relations.
- fixed foreign key names on MySQL (and possibly other) databases by 
  making sure the generated name is unique for the whole database, and not
  only for the table on which it applies.
- corrected some docstrings

0.1.0 - 2007-02-12
initial release