root / elixir / trunk / CHANGES @ 480

Revision 480, 23.8 kB (checked in by ged, 5 years ago)

- Provide our own Session.mapper equivalent to avoid SQLAlchemy 0.5.5+

deprecation warning. This mapper autosave object instances on init unless
save_on_init=False is passed as a mapper argument (closes #92).

- simplified a few tests in test_options.py

Line 
10.7.0 - 2009-09-xx
2
3Please see http://elixir.ematia.de/trac/wiki/Migrate06to07 for detailed
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!
6
7New features:
8- Added a new statement 'using_options_defaults' which can be used
9  on a custom base class to set default values for the options of all its
10  subclasses. For example, this makes it possible to have all classes
11  inheriting from your custom base class use some custom options without
12  having to set it individually on each entity, nor modify
13  options.options_defaults.
14- The local_colname and remote_colname arguments on ManyToMany relationships
15  can now also be used to set custom names for the ManyToMany table columns.
16  This effectively replace the column_format on ManyToMany relationships which
17  is now deprecated. Change based on a patch from Diez B. Roggisch.
18- Added (or rather fixed and documented) a "table" argument on ManyToMany
19  relationships to allow using a manually-defined Table (closes #44).
20- Added a "schema" argument on ManyToMany relationships to be able to create
21  the ManyToMany table in a custom schema and not necessarily the same schema
22  as the table of the "source" entity (patch from Diez B. Roggisch).
23- Added a "table_kwargs" argument on ManyToMany relationships to pass any
24  extra keyword arguments to the underlying Table object (closes #94).
25- Added a new "target_column" argument on ManyToOne relationships so that you
26  can target unique but non-primary key columns. At the moment, this only works
27  if the target column is declared before the ManyToOne (see ticket #26).
28- Added new "column_names" argument to the acts_as_versioned extension,
29  allowing to specify custom column names (inspired by a patch by
30  Alex Bodnaru).
31- Made M2MCOL_NAMEFORMAT option accept a callable, so that more complex naming
32  generation can be used if so desired.
33- Added two new extensions (contributed by Alex Bodnaru)
34  - "perform_ddl" allows to execute one or several DDL statements upon table
35    creation.
36  - "preload_data" allows to insert data into the entity table just after it
37    has been created.
38- EntityCollection gained a working extend method
39
40Changes:
41- Moved class instrumentation to a separate function: instrument_class
42- Moved all methods of the "Entity" base class, to the "EntityBase" class, so
43  that people who want to provide their own base class but don't want to loose
44  all the methods provided by "Entity" can simply inherit from EntityBase
45  instead of copy-pasting the code for all its methods.
46- Renamed remote_side and local_side ManyToMany arguments to remote_colname and
47  local_colname respectively to not collide with the remote_side argument
48  provided by SA (it doesn't make much sense on ManyToMany relationships but
49  still).
50- Delete Elixir properties in the setup phase rather than as soon as they are
51  attached to their class. It makes it possible to access them or refer to them
52  after the class is defined (but before setup).
53- Deprecated act_as_list extension in favor of SQLAlchemy's orderinglist
54  extension (closes #53).
55- Made manually defined mapper options take precedence over Elixir-generated
56  ones. Not very useful yet since most are expecting Column objects.
57- Default table_options (defined in options_defaults['table_options']) are now
58  also used for ManyToMany tables (closes #94).
59- Provide our own Session.mapper equivalent to avoid SQLAlchemy 0.5.5+
60  deprecation warning. This mapper autosave object instances on __init__ unless
61  save_on_init=False is passed as a mapper argument (closes #92).
62
63Bug fixes:
64- Fixed Elixir to work with the future SQLAlchemy 0.6 (trunk as of 6377).
65- Changed the pattern used by default to generate column names for (all)
66  ManyToMany relationships so that the meaning of bidirectional
67  self-referential relationships does not depend on the order of declaration
68  of each side (closes #69). See upgrade notes for details.
69- Changed slightly the pattern used to generate the name of the table for
70  bidirectional self-referential ManyToMany relationships so that it doesn't
71  depend on the order of declaration of each side (closes #19).
72  See upgrade notes for details.
73- default EntityCollection raise an exception instead of returning None when
74  trying to resolve an inexisting Entity from outside of another entity (for
75  example through EntityCollection.__getattr__
76- Fixed the case where you specify both "primaryjoin" and "colname" arguments
77  (useless in this case, but harmless) on a ManyToOne relationship of an
78  autoloaded entity.
79- Fixed bug which broke the "identity" (Entity) option
80- Fixed documentation about local_side and remote_side arguments being
81  required if the entity containing the relationship is autoloaded, when it is
82  only required if the relationship is self-referencial, and primaryjoin or
83  secondaryjoin as not been specified manually.
84- Added missing documentation for the "filter" argument on OneToMany
85  relationships.
86- Fixed the act_as_list extension's move_to_bottom method to work on MySQL
87  (closes #34).
88- Fixed event methods not being called when they are defined on a parent class.
89  (introduced in release 0.5.0).
90- Added workaround for an odd mod_python behavior (class.__module__ returns a
91  weird name which is not in sys.modules).
92- Fixed filter argument on OneToMany relationship leaking the filter to the
93  unfiltered relationship.
94- Fixed encrypted extension to not encrypt several times an instance attributes
95  when that instance is flushed several times before being expunged from the
96  session.
97- Fixed using to_dict with a ManyToOne relationship in the "deep" set and that
98  relationship being None in the entity being converted.
99
1000.6.1 - 2008-08-18
101
102New features:
103- Allow ManyToOne relationships to use manually created fields as their
104  "supporting column". This means that the columns can be customized without
105  resorting to using the ugly "column_kwargs" (patch from Jason R. Coombs,
106  closes #39).
107- Extra args and kwargs to Synonym and ColumnProperty are forwarded to their
108  underlying constructs. This allows for example deferred ColumnProperties.
109- Added a more helpful assertion message when inverse relationship types don't
110  match.
111
112Changes:
113- Removed support for the deprecated "with_fields" syntax
114- Entity.__init__ calls Entity.set instead of duplicating its functionality
115
116Bug fixes:
117- Fixed the "Target resolves to several entities" exception message to actually
118  include the target name.
119- Renamed the on_reconstitute method decorator to reconstructor, to track the
120  corresponding change in SA's trunk.
121
1220.6.0 - 2008-07-18
123
124Please see http://elixir.ematia.de/trac/wiki/Migrate05to06 for detailed
125upgrade notes.
126
127New features:
128- Fields in a custom base class are added to all their children.
129- Added two new methods on the base entity: from_dict and to_dict, which can
130  be used to create (or output) a whole hierarchy of instances from (to) a
131  simple JSON-like dictionary notation (patch from Paul Johnston,
132  closes ticket #40).
133- Added experimental (!) support for concrete table inheritance (both
134  polymorphic or not). Concrete polymorphic inheritance requires SQLAlchemy
135  0.4.5 or later.
136- Moved the "entity to string" mapping and resolving code to the (newly
137  created) EntityCollection class (which stores lists of entities). This
138  allows one to provide a custom mapping method if needed. The default class
139  also overrides the __getattr__ method, providing and handy way to get at your
140  entities. See http://elixir.ematia.de/trac/browser/elixir/tags/0.6.0/tests/test_collections#L58
141- Added new "identity" option which can be used to set a custom polymorphic
142  identity for an entity. It also accepts a callable so that you can generate
143  the identity name automatically from the class itself.
144- Added __setattr__ method on Metaclass so that you can add properties
145  slightly more easily after class definition (but *before* setup_all):
146    class A(Entity):
147        pass
148    A.name = Field(String(32))
149- Added add_table_column, add_mapper_property and add_mapper_extension helper
150  methods in EntityBuilders.
151- Added full_tablename property on EntityDescriptor (includes schema name if
152  any).
153- Added on_reconstitute event/method decorator. Only works with SA 0.5.
154- Added support for viewonly relationships (OneToMany and OneToOne).
155- Added support for filtered OneToMany relationships. Produce viewonly
156  relations. See http://elixir.ematia.de/trac/browser/elixir/tags/0.6.0/tests/test_o2m.py
157  for an example.
158- Added support for callables for some arguments on relationships: primaryjoin,
159  secondaryjoin and remote_side. It means those can be evaluated at setup time
160  (when tables and their columns already exist) instead of definition time.
161
162Changes:
163- Default "target entity resolving code" changed slightly. It now uses a global
164  collection keyed on the entity name. This means that entities can refer to
165  other entities in a different module simply with the target entity name
166  instead of its full path. The full path is only required when there is an
167  ambiguity (ie when there are two classes with the same name in two different
168  modules). Closes #9.
169- Added support for SQLAlchemy 0.5, and dropped support for version 0.3 and
170  earlier.
171- The default session (elixir.session) uses sessionmaker() instead of
172  create_session(), which means it has now the following characteristics:
173    * autoflush=True
174    * autocommit=False (with SA 0.5 -- equivalent to transactional=True with
175      SA 0.4)
176    * autoexpire=True (with SA 0.5).
177- removed objectstore and other SA 0.3 (or older) support code.
178
179Bug fixes:
180- Fixed multi-table inheritance when using a non default schema (closes #38)
181- Fixed ManyToOne relationships using 'key' kwarg in their column_kwargs
182  (patch by Jason R. Coombs)
183- Fixed inheritance with autoloaded entities: when using autoload, we
184  shouldn't try to add columns to the table (closes tickets #41 and #43).
185- Fixed acts_as_list extension with autoloaded entities (patch from maqr,
186  closes ticket #52).
187- Fixed ColumnProperty to work with latest version of SQLAlchemy (O.4.5 and
188  later)
189- Fixed ManyToMany relationships when not using the default schema
190  (patch from Diez B. Roggisch, closes ticket #48)
191
192Misc:
193- Added AUTHORS list. If you are missing from this list, don't hesitate to
194  contact me.
195
1960.5.2 - 2008-03-28
197
198New features:
199- Added an optional `check_concurrency` keyword argument to the versioning
200  extension, supporting the usage of SQLAlchemy's built-in optimistic
201  concurrency check.
202
203Changes:
204- Made Elixir python 2.3 compatible again (based on patches from
205  Jason R. Coombs)
206
207Bug fixes:
208- Fixed act_as_list extension to work with DBMS that require subselects to be
209  aliased (patch by Alice McGregor)
210- Fixed the versioning extension so that the history table is updated within
211  the current transaction (patch from and closes ticket #35).
212
2130.5.1 - 2008-02-07
214
215New features:
216- Added a new elixir plugin for managing entities as (ordered) lists.
217- Added a `column_format` keyword argument to `ManyToMany` which can be used
218  to specify an alternate format string for column names in the mapping table.
219- Added support for custom base classes which inherit from another class (ie
220  not directly from object).
221- Added an alternate (nicer) syntax to define synonym properties.  This syntax
222  has a more limited scope, except that it can refer to properties defined in
223  a parent entity. This is based on a patch from Alexandre da Silva.
224
225Changes:
226- Added check so that using an inexisting column in an order_by or other
227  column-name based argument raises an exception.
228- The polymorphic_identity kwarg in using_mapper_options is not overriden
229  anymore by the one generated by Elixir (patch from Ben Bangert).
230- Moved the format of the multi-table inheritance column to a constant in
231  options (so that it can be changed globally).
232- The foreign key constraint of the column in a multi-table inheritance is
233  configured with a cascade rule.
234
235Bug fixes:
236- A child entity doesn't inherit anymore its parent entity statements (such as
237  options) if it doesn't use any statement itself.
238- Made inheritance work for custom base classes (closes #25).
239- Fixed the inverse relationship matching when the inverse relationship is
240  defined in a parent Entity (thanks to Alexandre da Silva).
241- Fixed bug in setup_entities (it always used the global entity list and not
242  the list given as argument).
243- Fixed the versioning extension not appropriately handling versioned
244  entities with onupdate events (patch from Remi Jolin, closes #29).
245- Fixed videostore example (patch from Jason R. Coombs, closes #31).
246
2470.5.0 - 2007-12-08
248
249Please see http://elixir.ematia.de/trac/wiki/Migrate04to05 for detailed
250upgrade notes.
251
252New features:
253- Added set method on base Entity (set attributes using kwargs)
254
255Changes:
256- Autosetup defaults to False ! (please look at those upgrade notes!)
257- Polymorphic defaults to True (inheritance is polymorphic by default).
258- Removed one of the autosetup triggers altogether: there is no "fake" mapper
259  registered in SQLAlchemy's mapper_registry anymore, so if you try to
260  access the class mapper directly (not through the 'mapper' attribute on
261  the class), before the setup phase happens, it won't work. This was done
262  because of a change in SQLAlchemy trunk (future SA 0.4.2) which broke that
263  piece of code (and prevented to use autosetup at all). Since that code
264  was a hack in the first place, instead of doing some even uglier hackery,
265  I got rid of it altogether.
266- Moved some format strings to constants in options, so that one can change
267  them if he wants to.
268- Allow overriding primary_key columns on autoloaded entities (closes tickets
269  #20 and #22)
270- Columns created by ManyToOne relationships can now optionally (through
271  column_kwargs) *not* create an index (ie it's not harcoded anymore).
272  Suggestion by Jason R. Coombs.
273
274Bug fixes:
275- Fixed a nasty bug which prevented inheritance to work correctly when using
276  the attribute syntax in many cases.
277- Fixed associable extension to work with SQLAlchemy trunk (future 0.4.2).
278- Fixed an incompatibility with zope.interfaces.
279- Tweaked the initialization sequence again (in fact revert an older change)
280  which prevented to reuse class properties of one class in other (subsequent)
281  classes.
282- Fixed our tests to work with SA trunk (future 0.4.2) (unicode data + use of
283  deprecated attributes)
284
2850.4.0 - 2007-10-29
286
287Please see http://elixir.ematia.de/trac/wiki/Migrate03to04 for detailed
288upgrade notes.
289
290New features:
291- Implemented a new syntax to declare fields and relationships, much closer to
292  what is found in other Python ORM's. The with_fields syntax is now
293  deprecated in favor of a that new syntax. The old statement based (has_field
294  et al.) syntax is still available though (and will remain so for quite some
295  time). This was done with help from a patch by Adam Gomaa.
296- Implemented polymorphic single-table inheritance as well as polymorphic and
297  non-polymorphic multi-table (aka joined table) inheritance.
298- Added ext sub-package for additional Elixir statements.
299- Added associable extension for generating polymorphic associations with
300  Elixir statements.
301- Added versioning extension to keep track to all changes to your entities by
302  storing them in a secondary table.
303- Added encryption extenstion to encrypt/decrypt some fields data on the fly
304  when writing to/reading from the database.
305- Added support for synonym properties.
306- Added shortcut syntax to define column_properties.
307- Added a .query attribute on all entities. The old .query() syntax is still
308  available.
309- Added support to add any SQLAlchemy property on your mapper, through the
310  GenericProperty class (as well as the has_property statement). These can
311  work even if they rely on the entity columns (an thus need them to be
312  defined before the property can be declared). See tests/test_properties.py
313  for examples.
314- Added support for "manual session management" (ie you can now define an
315  entity with "using_options(session=None)" and it won't use any
316  SessionContext extension, nor receive the "query" attribute.
317- Made the statement system more powerfull.
318
319Changes:
320- The setup time was changed. That is the table and mapper are not created as
321  soon as the class is defined, but rather when first used, or when explicitly
322  calling the setup function (recommended). This also allowed us to reorder
323  the setup process and allows, among others to use a ManyToOne-generated
324  column as a primary key, to use unique constraints on those columns, to
325  order by those columns and so on...
326- Made Elixir work with both SQLAlchemy 0.4 and 0.3.10 (with help from a patch
327  by Ants Aasma).
328- Moved away from assign_mapper, now all assign_mapper-provided methods are on
329  the Entity class. Now, if people don't like them, they have the option to
330  simply provide another base class.
331- Default objectstore is now a ScopedSession when working on SQLAlchemy 0.4.
332  It means that it's not wrapped in an Objectstore object at all. This means,
333  that depending on the version of SA you are using, you'll get a slightly
334  different behavior.
335- Relationships to other classes can now also be defined using the classes
336  themselves in addition to the class namees. Obviously, this doesn't work for
337  forward references.
338- Classes defined inside a function can now have relationships to each other.
339- Added default __init__ method on entities so that subclasses can override it
340  and still have the "set attribute by keyword" behavior by calling super()
341- Added "through" and "via" keyword arguments on relationships and has_field
342  statement, to proxy values through relationships (uses association_proxy)
343- Made EntityMeta public, so that people can actually define their own base
344  class.
345- Changed the order of relationship kwargs processing so that computed kwargs
346  can be overridden by kwargs manually passed to the statement. This should
347  only be used if you know what you are doing.
348- Added onupdate kwarg to BelongsTo relationships for consistency with the
349  ondelete kwarg
350- Added ondelete and onupdate kwargs for use with has_and_belongs_to_many
351  to apply on delete clauses to foreign key constraints on the m2m table.
352- Columns of the intermediary table of an has_and_belongs_to_many relationship
353  are now marked as primary keys.
354- Reworked how entities look for primary keys on related entities. This
355  enables one "normal" entity (fully defined in Elixir) to refer to an entity
356  which is autoloaded.
357- Added translation (from column name to column object) of the primary_key
358  mapper option so that it can actually be used. This allows to have entities
359  without any primary key defined at the table level.
360- Added the possibility to give a custom name for ManyToOne constraints
361  (patch from and closes ticket #16)
362- Dropped support for the old threadlocal SA extension (which doesn't even exist
363  anymore in SA 0.4)
364
365Bug fixes:
366- Reworked/cleaned tests so that they don't leak stuff to other tests (both at
367  the method level and module level) anymore. Uses nosetest's module level
368  fixture.
369- Fixed relationships to entities whose primary_key field has been defined
370  with a "key" argument (based on a patch by Paul Johnston).
371- Fixed some buggy tests.
372- Fixed relationships to tables using a schema (patch by Neil Blakey-Milner)
373- Made inverse relationships use backrefs. This fixes the "bidirectional
374  coherency" problem some people had before doing a flush. (based on a patch
375  from Remi Jolin).
376
3770.3.0 - 2007-03-27
378- Made the provided metadata not threadlocal. This could break things for you
379  in some rare case. Please see the (newly created) FAQ file for details about
380  this.
381- Added support for autoloading/reflecting databases with
382  has_and_belongs_to_many relationships. The tablename argument is now
383  optional, but still recommended, otherwise you'll have to use the same exact
384  name for your intermediary table than the one generated. You also _have to_
385  specify at least one of either local_side or remote_side argument.
386- Added support for the "version_id_col" option on entities. This option adds
387  a column to the table which will be used to prevent concurrent modifications
388  on any row of the entity's table (i.e. it will raise an error if it happens).
389- Made the colname argument optional for belongs_to relationships in
390  autoloaded entities. It is only required to specify it if you have several
391  belongs_to relationships between two entities/tables.
392- Applied patch from "Wavy" so that columns of a table are in the same order
393  as they were declared (this only works for the has_field statement).
394- Applied patch from Isaac Csandl to add an "ondelete" argument to
395  belongs_to relationships. The content of that argument is forwarded to the
396  foreign key constraint.
397- Foreign key names generated by belongs_to relationships use column names
398  instead of relation names in case we have a relation with the same name
399  defined in several entities inheriting from the same entity using single-
400  table inheritance (and we set a custom column name in one of them to avoid
401  a column-name conflict).
402- Using invalid options on entities will now raise an exception
403- Added __version__
404- Use an explicit metaclass for entities, so that people can define their own
405  base class.
406- Changed the approach to reflecting/autoloading belongs_to relationships.
407  This shouldn't change anything to how it's used but allowed me to factor
408  some code with has_and_belongs_to_many relationships.
409- The tablename option can now be given a callable so that people can provide
410  their own function to get the table name for an entity. The tablename option
411  can now also be set globally (using the options_defaults dictionary). Of
412  course, this only makes sense for the callable usecase.
413
414- Fixed bug preventing having entities without any statement.
415- Fixed documentation for belongs_to relationships (the arguemnt is "required",
416  not "nullable").
417- Fixed typo which broke the use_alter argument on belongs_to relationships.
418- Fixed inheritance unit test to pass SQLAlchemy type check on relations
419  (introduced in SA 0.3.6)
420- Fixed wrong field length in autoload test (it was not noticeable with sqlite).
421- Actually make the code python 2.3 compatible (Robin's patch was based on
422  0.1.0 while I had introduced more decorators in the trunk in the mean time).
423
424- Made some PEP8 tweaks in many places. Used the pep8 script provided with
425  Cheesecake.
426- Some cleanup/useless code removal
427
4280.2.0 - 2007-02-28
429- Applied patch from Robin Munn to make the code python 2.3 compatible
430- Per a suggestion on the mailing list, look at the calling stack frame to
431  ensure that we apply statements to the proper class.  We now attach the
432  statement list to the class itself, rather than attaching it to a global
433  list that is neither threadsafe, nor safe when doing nested class
434  definition.  Also added a test to validate that this works.
435- implemented singletable non-polymorphic inheritance
436- added support to pass non-keyword arguments to tables. You just pass
437  them to the using_table_options statement and they will be forwarded to the
438  table along with the keyword arguments. This can be used to set table
439  constraints.
440- added support for deferred columns (use the "deferred" keyword argument on
441  fields)
442- added a "required" keyword argument on fields and BelongsTo
443  relationships. This is the opposite of the "nullable" SA argument.
444- added a "column_kwargs" keyword argument to BelongsTo relationships
445  to forward any keyword argument directly to the SA Column.
446- added support for the use_alter and constraint_kwargs kwargs on BelongsTo
447  relationships (forwarded to SA ForeignKeyConstraint).
448    -> removed the systematic use_alter on BelongsTo relations since it
449       can now be specified only when needed.
450    -> removed it from HasAndBelongsToMany relations, since I think a
451       circular foreign key dependency can't happen with those relations.
452- fixed foreign key names on MySQL (and possibly other) databases by
453  making sure the generated name is unique for the whole database, and not
454  only for the table on which it applies.
455- corrected some docstrings
456
4570.1.0 - 2007-02-12
458initial release
Note: See TracBrowser for help on using the browser.