Timeline
12/10/08:
- 17:46 Ticket #63 (Need to create predictable names for unique indexes on columns) created by
- Currently, we use ... UNIQUE, which means you can't delete the column's …
- 17:04 Ticket #62 (Unit tests do not test add_column) created by
- Since I broke it today, and the unit tests didn't catch it.
12/09/08:
- 13:37 Ticket #61 (CONSTRAINT fails on uppercase characters in column names) created by
- The ALTER TABLE ADD CONSTRAINT commands fails when column names contain …
12/08/08:
- 15:40 Ticket #60 (many-to-many self reference - can't do this) created by
- I've got Article model which is inheriting from BaseArticle? model. Article …
12/07/08:
- 15:12 Ticket #57 (A column add example in the docs?) closed by
- fixed: Fixed; I've added a tutorial section, and a quick reference in the command …
- 15:12 CommandReference edited by
- (diff)
- 15:09 Tutorial edited by
- (diff)
- 15:03 Ticket #59 (Add --add-field option to startmigration) closed by
- fixed: Done in [108] and [109] - I've run it through a series of quick tests, but …
12/06/08:
- 21:20 Ticket #59 (Add --add-field option to startmigration) created by
- Something like: […] which would create the template with the …
- 21:13 Ticket #58 (Attribute errors cause MySQL to partially apply a migration) closed by
- fixed: Fixed in [107], including subtle please-oh-god-not-mysql hint.
- 20:40 Ticket #58 (Attribute errors cause MySQL to partially apply a migration) created by
- Migration with […] will obviously not work, but mysql won't rollback …
- 19:35 Ticket #57 (A column add example in the docs?) created by
- Since column adds are 80% of our migrations (and I would assume many …
12/03/08:
- 19:30 Ticket #56 (./manage.py migrate breaks for apps with no migrations) closed by
- fixed: Fixed in [105].
- 14:50 Ticket #56 (./manage.py migrate breaks for apps with no migrations) created by
- If you define an app as being handled by south, but you've yet to create …
- 09:37 Ticket #55 (post_syncdb signal is sent too early) created by
- Our app is listening to post_syncdb signal to load some initial data …
12/02/08:
- 00:03 Ticket #54 (alter_column has null-ness swapped) closed by
- fixed: OK, fixed in [103] and [104]. I had to rewrite null_ok to use basic SQL; …
12/01/08:
- 19:35 Ticket #54 (alter_column has null-ness swapped) created by
- Looking in alter_column in generic.py, the set_null and drop_null are …
11/30/08:
- 22:01 Ticket #16 (No way to provide initial data for models) closed by
- fixed: No, that wasn't intentional. It's fixed in [102]. Since that looks like …
- 21:22 Ticket #53 (error when default callable is static method) closed by
- wontfix: Now, this is difficult, as the whole reason MockModels? exist is because …
- 01:34 Ticket #53 (error when default callable is static method) created by
- File "/var/djangoapps/proj/app/migrations/0001_initial.py", line 49, in …
11/28/08:
- 22:21 Ticket #52 (Implement SQLite alter/rename/drop column via workarounds) created by
- Currently these just raise exceptions in the SQLite commands, but it would …
- 22:18 Ticket #51 (Sqlite3 does not support dropping of columns) closed by
- fixed: Fixed in [100], by just adding a nice error, like we have for …
- 22:12 Ticket #51 (Sqlite3 does not support dropping of columns) created by
- Regarding http://www.sqlite.org/lang_altertable.html Sqlite3 does not …
- 18:35 Ticket #2 (problems with multi-table inheritance) closed by
- fixed
- 18:00 DatabaseAPI edited by
- (diff)
- 17:57 Ticket #50 (simplify the "add not-null fields" case) closed by
- fixed: Fixed in [98]. Just do: […]
- 17:07 Ticket #50 (simplify the "add not-null fields" case) created by
- imagine that you have a model: […] now you add a new field to it, so …
11/25/08:
- 23:06 Ticket #49 (vanilla 'migrate' command isn't explained in the docs) closed by
- fixed: A good point. I've extended the Command Reference …
- 23:05 CommandReference edited by
- (diff)
- 20:49 Ticket #49 (vanilla 'migrate' command isn't explained in the docs) created by
- You do a great job of explaining the nuances of {{{./manage.py migrate …
11/24/08:
- 14:50 Ticket #47 (Automatic initial migration generation fails when models.py does not end ...) reopened by
- 14:49 Ticket #47 (Automatic initial migration generation fails when models.py does not end ...) closed by
- fixed: This appears to be a bug in the inspect module - it's not returning that …
- 14:47 Ticket #48 (startmigration should support model inheritance) closed by
- fixed: Fixed in [97].
- 14:25 Ticket #48 (startmigration should support model inheritance) created by
- Currently startmigration fails on the special _ptr fields model …
- 14:24 ConvertingAnApp edited by
- (diff)
- 02:27 Ticket #47 (Automatic initial migration generation fails when models.py does not end ...) created by
- If one executes the command "./manage.py startmigration --initial …
11/22/08:
- 15:40 Ticket #21 (Default values don't work with mysql) closed by
- duplicate: This is a duplicate of #14, as far as I see it.
- 15:32 Ticket #31 (Confusing error in startmigration --initial if the directory already ...) closed by
- fixed: Fixed in [95], by creating the init.py.
- 00:06 Ticket #43 (Column renames in mysql don't handle default value types correctly) closed by
- fixed: Fixed in [94].
- 00:00 Ticket #39 (MySQL and index creation problem.) closed by
- invalid: Unfortunately, this is a limitation of your MySQL; your installation seems …
11/21/08:
- 13:41 Ticket #46 (Support for MSSQL (django-pyodbc)) created by
- django-pyodbc <http://code.google.com/p/django-pyodbc/> provides support …
11/20/08:
- 23:28 Ticket #44 (Invalid code generated by startmigration --initial) closed by
- duplicate: Deplicate of #45
- 23:03 Ticket #45 (Invalid code generated by startmigration --initial) created by
- I get totally invalid Python code when using startmigration --initial
- 23:03 Ticket #44 (Invalid code generated by startmigration --initial) created by
- I get totally invalid Python code when using startmigration --initial
- 22:56 About edited by
- (diff)
- 22:45 Ticket #34 (Sqlite3 not supported) closed by
- fixed: I did go ahead and add this note to the main page, but then decided …
- 22:25 Ticket #40 (delete_index syntax incorrect for MySQL) closed by
- fixed: Fixed in [92]. There's even a unit test for it now!
- 21:52 Ticket #42 (--verbosity problem in migrate.py) closed by
- fixed: Looks alright - thanks for the patch. Fixed in [91].
- 21:45 About edited by
- (diff)
11/19/08:
- 22:06 Ticket #43 (Column renames in mysql don't handle default value types correctly) created by
- An example of this issue is that renaming a column doesn't quote strings …
- 05:34 Ticket #42 (--verbosity problem in migrate.py) created by
- The problem in #27 also exists in the migrate.py command. --verbosity is …
- 04:44 Ticket #41 (Handling of fields in startmigration creates problematic code dependencies) created by
- By default startmigration just copies fields making create_table input …
11/18/08:
- 05:43 Ticket #40 (delete_index syntax incorrect for MySQL) created by
- South currently uses a generic statement: 'DROP INDEX index_name' For …
11/17/08:
- 10:59 Ticket #39 (MySQL and index creation problem.) created by
- My migration is defined like: […] It works well with PostgreSQL but …
11/15/08:
- 22:49 Ticket #38 (Verbosity option has no fallback) closed by
- fixed: Yup, that looks about right - good point. I've checked in [90], which …
- 22:19 Ticket #38 (Verbosity option has no fallback) created by
- Since the verbose option was added, I can't call "migrate" by …
11/14/08:
- 10:34 Ticket #37 ([patch] bug in loading initial data) closed by
- fixed: Fixed in [89].
11/13/08:
Note: See TracTimeline
for information about the timeline view.
