Timeline
03/18/10:
- 22:24 MyFieldsDontWork edited by
- (diff)
- 21:29 WikiStart edited by
- (diff)
- 21:27 WikiStart edited by
- (diff)
- 21:25 WikiStart edited by
- (diff)
- 21:04 Ticket #385 (First migrate after initial set up) closed by
- worksforme: Yes, 0.7 supports Django 1.2. I'm in the process of releasing 0.7 RC1 now, …
- 20:26 OldDocumentation created by
- 20:04 Ticket #373 (inherited keyword arguments passed to a model causes an exception) closed by
- fixed: It wasn't quite "tomorrow" - sorry - but committed in [2d9586a718b2].
- 20:02 Ticket #384 (Adding a OneToOne relation fails) closed by
- fixed: Fixed in [a72454a60f66].
- 19:54 Ticket #386 (logging defect) closed by
- fixed: Fixed in [2835d255442d].
- 19:50 Ticket #387 (defect in logger test) closed by
- fixed: Fixed in [5a708caca66f].
- 19:39 Ticket #381 (South tests fail) closed by
- fixed: Fixed in [00df6d09c374].
- 16:28 Ticket #387 (defect in logger test) created by
- In test_db_execute_logging_validfile function, you are trying to remove …
- 16:10 Ticket #386 (logging defect) created by
- Every time when sql query processed, execute(…) method of …
03/17/10:
- 20:50 Ticket #385 (First migrate after initial set up) created by
- The commands I've run (removing corporate information): $./manage.py …
- 20:20 Ticket #380 (SQLite and removing columns) closed by
- fixed: Fixed in [2df0a676a47d].
- 20:17 Ticket #377 (alter_column failing on SqLite when specifying the column name of ...) closed by
- fixed: Fixed in [eb5a5f86d57a].
- 20:16 Ticket #383 (altering sqlite columns creates invalid sql) closed by
- fixed: Fixed in [eb5a5f86d57a].
- 19:53 Ticket #376 (addding db_index not executed) closed by
- fixed: An excellent bug report, with one small issue; in the example, you've …
- 16:50 Ticket #379 (DB module not detected with Django settings in multi-db format) closed by
- invalid: 0.6.2 is not compatable with Django 1.2; 0.7, the current development …
- 16:44 Ticket #384 (Adding a OneToOne relation fails) created by
- My migration basically looks like this: […] Which looks pretty …
- 16:39 Ticket #382 (sqlite table recreation: not enough quoting) closed by
- fixed: Thanks for that; committed in [fb7089894e4d].
03/16/10:
- 12:51 Ticket #383 (altering sqlite columns creates invalid sql) created by
- the column name for altered columns was duplicated. for example: {{{{ …
- 11:55 Ticket #382 (sqlite table recreation: not enough quoting) created by
- If you model has a field with a reversed name, copying data from the …
- 00:53 Ticket #381 (South tests fail) created by
- I am at the latest development version. I tried testing South and got the …
03/15/10:
- 11:42 Ticket #380 (SQLite and removing columns) created by
- there seems to be a bit missing for sqlite column removal support; the …
- 00:01 Ticket #379 (DB module not detected with Django settings in multi-db format) created by
- Once settings.py is converted to multi-db format for database settings, …
03/13/10:
- 15:27 Ticket #378 (dashes in migration name causes South to not see them) created by
- While converting an existing app from South 0.6x to South 0.7pre I found …
03/12/10:
- 23:13 Ticket #377 (alter_column failing on SqLite when specifying the column name of ...) created by
- when executing the following migration step: […] I get the following …
- 14:45 Ticket #376 (addding db_index not executed) created by
- Adding an db_index=True fails to actually create an index in the database. …
03/10/10:
- 21:37 Ticket #183 (Changing the related model on a ForeignKey does not take care of ...) closed by
- fixed: Fixed in [4f86714a643e].
- 20:19 Ticket #371 (New --database option for migrate command doesn't work) closed by
- fixed: Fixed in [2273d7101099]. It was actually because "from x import y" imports …
- 13:55 Ticket #374 (import leaks) closed by
- fixed: This is (unfortunately) a WONTFIX; the datetime module has to be …
- 13:01 Ticket #374 (import leaks) created by
- When importing datetime in a migration, like this: from datetime import …
03/09/10:
- 16:08 Ticket #372 (initial_data is imported before necessary migrations have run, causing a ...) closed by
- fixed: Right, in that case I'll close it. (Yes, there's a few failing tests, I …
03/08/10:
- 18:47 Ticket #373 (inherited keyword arguments passed to a model causes an exception) created by
- If you have a model like the following: class Base(models.Model): …
- 12:44 Ticket #372 (initial_data is imported before necessary migrations have run, causing a ...) created by
- There's something a bit screwy about the order in which South applies …
03/05/10:
- 21:14 Ticket #371 (New --database option for migrate command doesn't work) created by
- I attempted using the --database option when migrating and noticed it …
03/04/10:
- 22:40 Ticket #370 (Extended MultiDB Support) created by
- Implement more sophisticated support for MultiDB. This will be support …
- 22:38 Ticket #365 (Automatically detect column renames) closed by
- duplicate: Duplicate of #358.
- 22:38 Ticket #369 (Specify database in migration class when using multiple databases) closed by
- wontfix: This is essentially a request for more sophisticated support for MultiDB; …
- 21:17 Ticket #369 (Specify database in migration class when using multiple databases) created by
- I've been testing out the --database=name option for the migrate command …
03/03/10:
- 19:47 Ticket #367 (exceptions.FailedDryRun called incorrectly) closed by
- worksforme: The exception is correctly raised in trunk; you seem to have an older dev …
- 19:45 Ticket #368 (South keeps default values for one-off values when adding a NOT-NULL ...) closed by
- fixed: In fact, you never want keep_default to be on, since that's not how Django …
- 19:41 Ticket #363 (South lists temporary files as migrations) closed by
- fixed
- 09:11 Ticket #368 (South keeps default values for one-off values when adding a NOT-NULL ...) created by
- After adding a NOT-NULL column to a model without a default value, South …
03/02/10:
- 15:29 Ticket #367 (exceptions.FailedDryRun called incorrectly) created by
- […]
- 09:05 Ticket #366 (Automatically create 3 migrations for changes which include data) created by
- When changing the schema, the docs recommend creating 3 migrations: * …
03/01/10:
- 17:06 Ticket #365 (Automatically detect column renames) created by
- Using some heuristics. See Migratory: …
- 17:05 Ticket #52 (Implement SQLite alter/rename/drop column via workarounds) closed by
- fixed: 0.7 fixes this.
- 17:03 Ticket #362 (Error auto creating backwards migration for custom fields) closed by
- fixed: Primary key error fixed in [a4e78540f46e].
- 16:37 Ticket #280 (Removing a OneToOneField Tries to add ID before before removing old PK) closed by
- fixed: South 0.7 now always puts field deletions first, so this bug is solved.
- 10:20 Ticket #364 (schemamigration and --stdout) closed by
- fixed: Fixed in [73b97f5f78b2].
- 10:15 Ticket #364 (schemamigration and --stdout) created by
- ./manage.py schemamigration book --auto --stdout aaa Migration names …
02/27/10:
- 13:05 Ticket #363 (South lists temporary files as migrations) created by
- Probably it should not think that files are directories. 0.6.2: […] …
- 12:37 Ticket #360 (Loaddata breaks in Django 1.2) closed by
- fixed: Committed as [6e99ee799d3f]. Thanks for the patch!
- 12:35 Ticket #361 (Failure to handle default value containing '%' character) closed by
- duplicate: You've reported this against 0.6.1, which is neither the most recent …
02/26/10:
- 22:26 Ticket #362 (Error auto creating backwards migration for custom fields) created by
- When I ran an auto migration on my schema from 0.6.2 to trunk, even though …
- 15:05 Ticket #361 (Failure to handle default value containing '%' character) created by
- South fails to handle text fields with default value containing '%' …
- 10:19 BadContent edited by
- (diff)
- 10:18 BadContent edited by
- (diff)
02/25/10:
- 14:30 Ticket #360 (Loaddata breaks in Django 1.2) created by
- LoadInitialDataMigrator? monkey patches django.models.get_app, so that the …
02/24/10:
- 20:57 Ticket #46 (Support for MSSQL (django-pyodbc)) closed by
- fixed: Ah, yes, this ticket has been languishing in here. We do indeed have SQL …
- 20:55 Ticket #359 (Failure Running Migrate) closed by
- fixed: Fixed in [2867a83f3ac7].
- 20:30 Ticket #359 (Failure Running Migrate) created by
- I just updated to the head of both django and south and when I try to run …
- 16:11 Ticket #281 (Anomaly when startmigration --auto adds one and removes another model) closed by
- fixed: I can't replicate this with 0.7, so marking as fixed.
- 15:42 WikiStart edited by
- (diff)
02/23/10:
02/22/10:
- 22:33 Ticket #275 (restrict migration names to be valid module names) closed by
- fixed: I've applied the fix that stops startmigration from allowing invalid …
- 22:19 Ticket #267 (--auto changing a field from e.g. a CharField to a ForeignKey fails) closed by
- fixed: This works now in 0.7 - a rename is issued.
- 22:16 Ticket #323 (Traceback when createing a new migration with ManyToMany field) closed by
- invalid: Can't replicate this; closing as invalid.
- 22:13 Ticket #248 (Verbosity=2 doesn't print create index statements in db-dry-run) closed by
- fixed: Fixed in [b6bcef4bad1f].
- 22:00 Ticket #313 (add new blank=True CharField on SQLite results in OperationalError: ...) closed by
- wontfix: I'm deciding to WONTFIX this. My reasoning: * The field has null set …
- 21:39 Ticket #326 (problems with orm and multi-table inheritance) closed by
- fixed: This has been fixed along with #182 in [237ca3bb6d5d].
- 21:29 Ticket #301 (Introspection error with no EOL at end of file with PointField) closed by
- fixed: Introspection is now competely removed from 0.7, so this bug is vacuously …
- 21:28 Ticket #272 (Changing column type results in "no changed found" on SQLite) closed by
- fixed: This should be working now on the new SQLite backend we have in 0.7.
- 21:15 Ticket #324 (M2M join table not created with Django 1.2 alpha 1) closed by
- fixed: This is fixed in trunk.
- 21:14 Ticket #287 (Sequence of column rename, add, then re-rename fails on sqlite) closed by
- fixed: SQLite refactor done, this works locally. Marking as fixed.
- 21:11 Ticket #182 (Improper handling of _bases) closed by
- fixed: Fixed in [237ca3bb6d5d]. Finally :)
- 20:39 Ticket #294 (Acessing ManyToMany field pulls the wrong relationship) closed by
- fixed: This has now been confirmed as fixed in 0.7.
02/21/10:
- 22:41 Milestone 0.6.3 completed
- 22:40 Ticket #249 (Auto doesn't create correct indices for many-to-many join tables) closed by
- fixed: Fixed in [84e6a6f74fe8].
- 22:13 Ticket #266 (rename_column does not specify table name) closed by
- fixed: Fixed in 0.7.
- 22:12 Ticket #256 (alter_column on sqlite3 datetime field caused column type to change) closed by
- fixed: The SQLite backend has now been rewritten and fixed in 0.7, and I can't …
- 22:11 Ticket #247 (Custom Model Fields throw exception durring migration) closed by
- fixed: This is no longer a problem in 0.7, so closing (we fixed up the custom …
- 22:09 Ticket #228 (Problems with fakeORM and script migration) closed by
- fixed: This is now fixed in 0.7.
02/20/10:
- 23:18 Ticket #356 (Deleting GenericRelation / Support ignoring fields) closed by
- worksforme: Yup, looks good with my tests. Re-closing.
- 12:55 Ticket #354 (Application 'xxxx' has no migrations.) closed by
- fixed: Fixed in [0cf576f0effe].
02/19/10:
- 14:17 Ticket #357 (Allow modelintrospector value rules to represent a static value) closed by
- fixed: I've added the option for static introspection rule values in …
- 14:07 Ticket #356 (Deleting GenericRelation / Support ignoring fields) reopened by
- I should probably clarify; ignoring support is in trunk, and generics are …
- 14:04 Ticket #356 (Deleting GenericRelation / Support ignoring fields) closed by
- worksforme: This has already been implemented in trunk; see [3cac35d9a8ee].
- 14:04 Ticket #357 (Allow modelintrospector value rules to represent a static value) created by
- Currently, the way hidden fields need to be handled …
- 13:56 Ticket #356 (Deleting GenericRelation / Support ignoring fields) created by
- If a GenericRelation? is removed, it will be added to the migration as …
02/18/10:
- 23:41 Ticket #353 (MySQL dry run fail) closed by
- fixed: Fixed in [fce19051566e]. Thanks!
- 23:34 Ticket #355 (Addition for FAQ, or a warning somewhere for convert_to_south and migrate ...) closed by
- fixed: Yes, that would be a Bad Thing. It's pointed out several places in the …
- 23:15 Ticket #355 (Addition for FAQ, or a warning somewhere for convert_to_south and migrate ...) created by
- If you convert an existing app to South, that has data in the DB […] …
- 21:01 Ticket #354 (Application 'xxxx' has no migrations.) created by
- Im trying to convert my application to south with convert_to_south, when i …
- 18:03 ReleaseNotes/0.7 edited by
- (diff)
- 03:20 Ticket #353 (MySQL dry run fail) created by
- Exception FailedDryRun? must take two arguments, but at line 158 (see …
02/17/10:
- 23:11 Ticket #352 (format string as default value for field confuses south) closed by
- duplicate: Duplicate of #317. We've already fixed this in trunk; hopefully we'll be …
- 12:04 Ticket #352 (format string as default value for field confuses south) created by
- A model with a field such as: […] will cause south to fail with …
- 08:54 Documentation edited by
- (diff)
02/16/10:
- 15:15 Ticket #245 (utf-8 coding detection is not done) closed by
- fixed: Since south now uses introspection entirely, and converts all strings into …
Note: See TracTimeline
for information about the timeline view.
