Timeline


and

04/06/12:

18:47 Ticket #1058 (PostreSQL issues with alter commands) closed by andrew
worksforme: I've just tried to replicate this with both an alter_column on a …
00:04 Ticket #1057 (PostgreSQL index name differences prevent field indexes from being dropped) closed by andrew
fixed: Oops, forgot to mark this as pulled/fixed.

04/04/12:

15:45 Ticket #1060 (Upload the 0.7.4 tar package on the releases page) closed by andrew
fixed
15:36 Ticket #1060 (Upload the 0.7.4 tar package on the releases page) created by anonymous
01:35 Ticket #1059 (ImportError: cannot import name CASCADE with new South, Django 1.2) closed by andrew
fixed: Already fixed just after the release: …
00:24 Ticket #1059 (ImportError: cannot import name CASCADE with new South, Django 1.2) created by martin maney
Unconfirmed bug reported in #django-south. Sounds likely on the face of …

04/03/12:

13:27 Ticket #1053 (Making field unique fails on PostgreSQL with Django 1.4) closed by andrew
fixed: Fixed and properly tested as of [916f74766c26].
13:21 Ticket #578 (Boolean default values are not set correctly when adding new columns with ...) closed by andrew
fixed: Fixed in [916f74766c26].
10:40 Ticket #1053 (Making field unique fails on PostgreSQL with Django 1.4) reopened by shai@…
There is a test (south.tests.db.TestOperations.test_alter_unique) that …

04/02/12:

11:10 Ticket #1053 (Making field unique fails on PostgreSQL with Django 1.4) closed by andrew
fixed: Fixed in [fb2c64e3fbb5].
09:53 Ticket #1058 (PostreSQL issues with alter commands) created by segnalazioni@…
Applying migrations that involves alter_column on foreign keys or …

03/30/12:

22:34 Ticket #1057 (PostgreSQL index name differences prevent field indexes from being dropped) created by john@…
I think the patch for ticket #776 fixed MySQL but broke PostgreSQL in the …

03/29/12:

20:19 Ticket #1056 (Soft-match dependencies) closed by andrew
wontfix: I don't think this is a wise idea (and I'm marking it WONTFIX) because …
20:12 Ticket #1056 (Soft-match dependencies) created by r.tirrell@…
It'd be nice if migration dependency names could be specified in a similar …

03/26/12:

21:59 WikiStart edited by andrew
(diff)
09:14 Ticket #1055 (Warning in migration template: "use orm['fooapp.YourModel'] not from ...) created by guettli
I know it and you know it. But many don't: […] Please add this …

03/23/12:

21:17 Ticket #763 (on_delete option for foreign keys not picked up by south) closed by andrew
fixed: Committed as [9faade77e7b4]. Thanks.

03/22/12:

22:19 Ticket #1052 (db.create_table generates index name too long for mysql) closed by andrew
invalid

03/19/12:

15:54 Ticket #1053 (Making field unique fails on PostgreSQL with Django 1.4) created by armisael.silix@…
Hi there, this issue seems to appear only with Django 1.4, and only when a …
15:30 Ticket #523 (Cant change ForeginKey from null=False to null=True in MySQL) closed by andrew
fixed: Please don't re-open tickets - this particular bug _was_ fixed a while …
15:28 Ticket #523 (Cant change ForeginKey from null=False to null=True in MySQL) reopened by anonymous
This issue still exists.

03/17/12:

12:54 Ticket #1012 (South Migrations fail with Django 1.4's Timezone Aware Feature) closed by andrew
fixed
10:51 Ticket #1012 (South Migrations fail with Django 1.4's Timezone Aware Feature) reopened by atkinsonr@…

03/16/12:

22:40 Ticket #1052 (db.create_table generates index name too long for mysql) created by fexcoffi@…
Issue does not exist on 0.5: CREATE INDEX …

03/15/12:

15:21 Ticket #1012 (South Migrations fail with Django 1.4's Timezone Aware Feature) closed by andrew
worksforme: I've just tried and I cannot replicate this problem with the latest Django …

03/08/12:

21:42 Ticket #1051 (delete_unique method not working with MySQL 5.5.19) closed by andrew
duplicate: Duplicate of #747.
18:35 Ticket #1051 (delete_unique method not working with MySQL 5.5.19) created by rduenasf@…
Currently, the delete_unique method makes a call to …
Note: See TracTimeline for information about the timeline view.