Groups
Groups
Sign in
Groups
Groups
Django Evolution Changes
Conversations
About
Send feedback
Help
Django Evolution Changes
1–30 of 260
Mark all as read
Report group
0 selected
codesite...@google.com
4/12/10
[django-evolution] r167 committed - Updated the FAQ to reflect the change in project management.
Revision: 167 Author: freakboy3742 Date: Mon Apr 12 07:51:25 2010 Log: Updated the FAQ to reflect the
unread,
[django-evolution] r167 committed - Updated the FAQ to reflect the change in project management.
Revision: 167 Author: freakboy3742 Date: Mon Apr 12 07:51:25 2010 Log: Updated the FAQ to reflect the
4/12/10
codesite...@google.com
2
4/12/10
Issue 115 in django-evolution: Please provide a downloadable version of django-evolution or make it available using easy_install
Updates: Status: Accepted Owner: chipx86 Comment #1 on issue 115 by chipx86: Please provide a
unread,
Issue 115 in django-evolution: Please provide a downloadable version of django-evolution or make it available using easy_install
Updates: Status: Accepted Owner: chipx86 Comment #1 on issue 115 by chipx86: Please provide a
4/12/10
codesite...@google.com
4/9/10
Issue 116 in django-evolution: EvolutionException is being passed instead of string value to Django BaseCommand.style.ERROR()
Status: New Owner: ---- New issue 116 by jonathan.grot: EvolutionException is being passed instead of
unread,
Issue 116 in django-evolution: EvolutionException is being passed instead of string value to Django BaseCommand.style.ERROR()
Status: New Owner: ---- New issue 116 by jonathan.grot: EvolutionException is being passed instead of
4/9/10
codesite...@google.com
2/21/10
Issue 114 in django-evolution: Django Evolution doesn't convert ForeignKey to OneToOneField
Status: New Owner: ---- New issue 114 by ad...@jfsimon.fr: Django Evolution doesn't convert
unread,
Issue 114 in django-evolution: Django Evolution doesn't convert ForeignKey to OneToOneField
Status: New Owner: ---- New issue 114 by ad...@jfsimon.fr: Django Evolution doesn't convert
2/21/10
codesite...@google.com
1/28/10
Issue 113 in django-evolution: Foreign key to model.proxy not processed well + patch
Status: New Owner: ---- New issue 113 by trebor74hr: Foreign key to model.proxy not processed well +
unread,
Issue 113 in django-evolution: Foreign key to model.proxy not processed well + patch
Status: New Owner: ---- New issue 113 by trebor74hr: Foreign key to model.proxy not processed well +
1/28/10
codesite...@google.com
1/2/10
Issue 112 in django-evolution: Make changing primary_key property possible
Status: New Owner: ---- New issue 112 by dmitry.risenberg: Make changing primary_key property
unread,
Issue 112 in django-evolution: Make changing primary_key property possible
Status: New Owner: ---- New issue 112 by dmitry.risenberg: Make changing primary_key property
1/2/10
codesite...@google.com
12/8/09
Re: Issue 57 in django-evolution: changing the field type to a foreignKey doesn't work
Comment #1 on issue 57 by ca9lar: changing the field type to a foreignKey doesn't work http://
unread,
Re: Issue 57 in django-evolution: changing the field type to a foreignKey doesn't work
Comment #1 on issue 57 by ca9lar: changing the field type to a foreignKey doesn't work http://
12/8/09
codesite...@google.com
12/4/09
Issue 111 in django-evolution: Skip empty SQL statements
Status: New Owner: ---- New issue 111 by tilldu: Skip empty SQL statements http://code.google.com/p/
unread,
Issue 111 in django-evolution: Skip empty SQL statements
Status: New Owner: ---- New issue 111 by tilldu: Skip empty SQL statements http://code.google.com/p/
12/4/09
codesite...@google.com
2
10/23/09
Issue 99 in django-evolution: the auto_now attribute for a date field generates error when the field is "not null"
Comment #1 on issue 99 by Maris.Nartiss: the auto_now attribute for a date field generates error when
unread,
Issue 99 in django-evolution: the auto_now attribute for a date field generates error when the field is "not null"
Comment #1 on issue 99 by Maris.Nartiss: the auto_now attribute for a date field generates error when
10/23/09
codesite...@google.com
2
10/19/09
Issue 110 in django-evolution: SQLMutation should accept or reject if sql is a string and not a list
Comment #1 on issue 110 by tilldu: SQLMutation should accept or reject if sql is a string and not a
unread,
Issue 110 in django-evolution: SQLMutation should accept or reject if sql is a string and not a list
Comment #1 on issue 110 by tilldu: SQLMutation should accept or reject if sql is a string and not a
10/19/09
codesite...@google.com
10/2/09
Issue 109 in django-evolution: AddField: wrong columnname in SQL-statement (ForeignKey with OneToOne-Relation)
Status: New Owner: ---- New issue 109 by zegrep: AddField: wrong columnname in SQL-statement (
unread,
Issue 109 in django-evolution: AddField: wrong columnname in SQL-statement (ForeignKey with OneToOne-Relation)
Status: New Owner: ---- New issue 109 by zegrep: AddField: wrong columnname in SQL-statement (
10/2/09
codesite...@google.com
9/29/09
Issue 89 in django-evolution: KeyError: 'field_type'
Comment #21 on issue 89 by luke.leighton: KeyError: 'field_type' http://code.google.com/p/
unread,
Issue 89 in django-evolution: KeyError: 'field_type'
Comment #21 on issue 89 by luke.leighton: KeyError: 'field_type' http://code.google.com/p/
9/29/09
codesite...@google.com
9/29/09
Issue 104 in django-evolution: register django_evolution @pypi
Comment #1 on issue 104 by luke.leighton: register django_evolution @pypi http://code.google.com/p/
unread,
Issue 104 in django-evolution: register django_evolution @pypi
Comment #1 on issue 104 by luke.leighton: register django_evolution @pypi http://code.google.com/p/
9/29/09
codesite...@google.com
9/29/09
Issue 108 in django-evolution: runtime exception after patching to take account of forced usage of python 2.6
Status: New Owner: ---- New issue 108 by luke.leighton: runtime exception after patching to take
unread,
Issue 108 in django-evolution: runtime exception after patching to take account of forced usage of python 2.6
Status: New Owner: ---- New issue 108 by luke.leighton: runtime exception after patching to take
9/29/09
codesite...@google.com
9
9/12/09
Issue 81 in django-evolution: field type change with same db_type should not require any evolution
Comment #10 on issue 81 by lwcyphr: field type change with same db_type should not require any
unread,
Issue 81 in django-evolution: field type change with same db_type should not require any evolution
Comment #10 on issue 81 by lwcyphr: field type change with same db_type should not require any
9/12/09
codesite...@google.com
9/9/09
Issue 107 in django-evolution: dropping primary key constraint with uppercase characters fails
Status: New Owner: ---- New issue 107 by jan.ostrochovsky: dropping primary key constraint with
unread,
Issue 107 in django-evolution: dropping primary key constraint with uppercase characters fails
Status: New Owner: ---- New issue 107 by jan.ostrochovsky: dropping primary key constraint with
9/9/09
codesite...@google.com
9/9/09
Issue 106 in django-evolution: missing "_id" suffix when referencing multi-table-inherited class
Status: New Owner: ---- New issue 106 by jan.ostrochovsky: missing "_id" suffix when
unread,
Issue 106 in django-evolution: missing "_id" suffix when referencing multi-table-inherited class
Status: New Owner: ---- New issue 106 by jan.ostrochovsky: missing "_id" suffix when
9/9/09
codesite...@google.com
8/30/09
Issue 9 in django-evolution: AddField fails if there is data in a table and null=False
Comment #6 on issue 9 by bradley.ayers: AddField fails if there is data in a table and null=False
unread,
Issue 9 in django-evolution: AddField fails if there is data in a table and null=False
Comment #6 on issue 9 by bradley.ayers: AddField fails if there is data in a table and null=False
8/30/09
codesite...@google.com
8/15/09
[django-evolution] r166 committed - Added fix for v1.1 support under SQLite3.
Revision: 166 Author: freakboy3742 Date: Fri Aug 14 23:23:44 2009 Log: Added fix for v1.1 support
unread,
[django-evolution] r166 committed - Added fix for v1.1 support under SQLite3.
Revision: 166 Author: freakboy3742 Date: Fri Aug 14 23:23:44 2009 Log: Added fix for v1.1 support
8/15/09
codesite...@google.com
8/3/09
Issue 89 in django-evolution: KeyError: 'field_type'
Comment #19 on issue 89 by berislav.lopac: KeyError: 'field_type' http://code.google.com/p/
unread,
Issue 89 in django-evolution: KeyError: 'field_type'
Comment #19 on issue 89 by berislav.lopac: KeyError: 'field_type' http://code.google.com/p/
8/3/09
codesite...@google.com
7/29/09
Issue 85 in django-evolution: Recent django - optparse.OptionConflictError: option --verbosity: conflicting option string(s): --verbosity
Comment #2 on issue 85 by tomovo: Recent django - optparse.OptionConflictError: option --verbosity:
unread,
Issue 85 in django-evolution: Recent django - optparse.OptionConflictError: option --verbosity: conflicting option string(s): --verbosity
Comment #2 on issue 85 by tomovo: Recent django - optparse.OptionConflictError: option --verbosity:
7/29/09
codesite...@google.com
7/25/09
Issue 105 in django-evolution: django-evolution executes evolutions on invalid models
Status: New Owner: ---- New issue 105 by Lukasz.Langa: django-evolution executes evolutions on
unread,
Issue 105 in django-evolution: django-evolution executes evolutions on invalid models
Status: New Owner: ---- New issue 105 by Lukasz.Langa: django-evolution executes evolutions on
7/25/09
codesite...@google.com
7/18/09
Issue 104 in django-evolution: register django_evolution @pypi
Status: New Owner: ---- New issue 104 by yatiohi: register django_evolution @pypi http://code.google.
unread,
Issue 104 in django-evolution: register django_evolution @pypi
Status: New Owner: ---- New issue 104 by yatiohi: register django_evolution @pypi http://code.google.
7/18/09
codesite...@google.com
6/26/09
Issue 103 in django-evolution: model.option.managed=False is not processed well
Status: New Owner: ---- New issue 103 by trebor74hr: model.option.managed=False is not processed well
unread,
Issue 103 in django-evolution: model.option.managed=False is not processed well
Status: New Owner: ---- New issue 103 by trebor74hr: model.option.managed=False is not processed well
6/26/09
codesite...@google.com
6/19/09
Issue 89 in django-evolution: KeyError: 'field_type'
Comment #18 on issue 89 by gabriel.sgt: KeyError: 'field_type' http://code.google.com/p/
unread,
Issue 89 in django-evolution: KeyError: 'field_type'
Comment #18 on issue 89 by gabriel.sgt: KeyError: 'field_type' http://code.google.com/p/
6/19/09
codesite...@google.com
2
5/28/09
Issue 49 in django-evolution: In SQLite, adding null fields populates the field value with the field name
Comment #4 on issue 49 by smileychris: In SQLite, adding null fields populates the field value with
unread,
Issue 49 in django-evolution: In SQLite, adding null fields populates the field value with the field name
Comment #4 on issue 49 by smileychris: In SQLite, adding null fields populates the field value with
5/28/09
codesite...@google.com
5/27/09
Issue 58 in django-evolution: Adding a Boolean field causes problems with PostgreSQL
Comment #14 on issue 58 by AdrianElford: Adding a Boolean field causes problems with PostgreSQL http:
unread,
Issue 58 in django-evolution: Adding a Boolean field causes problems with PostgreSQL
Comment #14 on issue 58 by AdrianElford: Adding a Boolean field causes problems with PostgreSQL http:
5/27/09
codesite...@google.com
5/10/09
Issue 102 in django-evolution: Error when evolving from IntegerField to FloatField
Status: New Owner: ---- New issue 102 by paddyjoy: Error when evolving from IntegerField to
unread,
Issue 102 in django-evolution: Error when evolving from IntegerField to FloatField
Status: New Owner: ---- New issue 102 by paddyjoy: Error when evolving from IntegerField to
5/10/09
codesite...@google.com
2
5/9/09
Issue 89 in django-evolution: KeyError: 'field_type'
Comment #17 on issue 89 by corn13read: KeyError: 'field_type' http://code.google.com/p/django
unread,
Issue 89 in django-evolution: KeyError: 'field_type'
Comment #17 on issue 89 by corn13read: KeyError: 'field_type' http://code.google.com/p/django
5/9/09
codesite...@google.com
4/30/09
[django-evolution commit] r165 - Updated the SQLite backend to support the managed flag, introduced in trunk for Django v1.1.
Author: freakboy3742 Date: Thu Apr 30 04:24:56 2009 New Revision: 165 Modified: trunk/
unread,
[django-evolution commit] r165 - Updated the SQLite backend to support the managed flag, introduced in trunk for Django v1.1.
Author: freakboy3742 Date: Thu Apr 30 04:24:56 2009 New Revision: 165 Modified: trunk/
4/30/09