My favorites | Sign in
Project Home Wiki Issues
Checkout   Browse   Changes  
Changes to /trunk/NEWS
r194 vs. r197 Compare: vs.  Format:
Revision r197
Go to: 
/trunk/NEWS   r194 /trunk/NEWS   r197
1 version 0.6.1 (25-October-2010):
2 * Fixed compatibility problems with both Django 1.1 and Python 2.4.
3
4
1 version 0.6.0 (24-October-2010): 5 version 0.6.0 (24-October-2010):
2 * Added support for Django 1.2's ability to use multiple databases. 6 * Added support for Django 1.2's ability to use multiple databases.
3 7
4 This should use the existing routers used in your project. By default, 8 This should use the existing routers used in your project. By default,
5 operations will happen on the 'default' database. This can be overridden 9 operations will happen on the 'default' database. This can be overridden
6 during evolution by passing --database=dbname to the evolve command. 10 during evolution by passing --database=dbname to the evolve command.
7 11
8 Patch by Marc Bee and myself. 12 Patch by Marc Bee and myself.
9 13
10 14
11 version 0.5.1 (13-October-2010): 15 version 0.5.1 (13-October-2010):
12 * Made the evolve management command raise CommandError instead of 16 * Made the evolve management command raise CommandError instead of
13 sys.exit on failure. This makes it callable from third party software. 17 sys.exit on failure. This makes it callable from third party software.
14 Patch by Mike Conley. 18 Patch by Mike Conley.
15 19
16 * Made the evolve functionality available through an evolve() function 20 * Made the evolve functionality available through an evolve() function
17 in the management command, allowing the rest of the command-specific 21 in the management command, allowing the rest of the command-specific
18 logic to be skipped (such as console output and prompting). Patch 22 logic to be skipped (such as console output and prompting). Patch
19 by Mike Conley. 23 by Mike Conley.
20 24
21 * Fixed incorrect defaults on SQLite when adding null fields. (Bug #49) 25 * Fixed incorrect defaults on SQLite when adding null fields. (Bug #49)
22 26
23 On SQLite, adding a null field without a default value would cause the 27 On SQLite, adding a null field without a default value would cause the
24 field name to be the default. This was due to attempting to select the 28 field name to be the default. This was due to attempting to select the
25 field name from the temporary table, but since the table didn't exist, 29 field name from the temporary table, but since the table didn't exist,
26 the field name itself was being used as the value. 30 the field name itself was being used as the value.
27 31
28 We are now more explicit about the fields being selected and populated. 32 We are now more explicit about the fields being selected and populated.
29 We have two lists, and no longer assume both are identical. We also use 33 We have two lists, and no longer assume both are identical. We also use
30 NULL columns for temporary table fields unconditionally. 34 NULL columns for temporary table fields unconditionally.
31 35
32 Patch by myself and Chris Beaven. 36 Patch by myself and Chris Beaven.
33 37
34 38
35 version 0.5.0 (18-May-2010): 39 version 0.5.0 (18-May-2010):
36 * Initial public release 40 * Initial public release
Powered by Google Project Hosting