Re: [Django] #23557: annotate gives different results on postgresql and mysql

#23557: annotate gives different results on postgresql and mysql -+- Reporter: brian|Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #23557: annotate gives different results on postgresql and mysql

#23557: annotate gives different results on postgresql and mysql -+- Reporter: brian|Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #23557: annotate gives different results on postgresql and mysql

#23557: annotate gives different results on postgresql and mysql -+- Reporter: brian|Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #23557: annotate gives different results on postgresql and mysql

#23557: annotate gives different results on postgresql and mysql -+- Reporter: brian|Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #22738: Schema migration: test_add_field_temp_default_boolean

#22738: Schema migration: test_add_field_temp_default_boolean -+- Reporter: maxi |Owner: nobody Type: | Status: new

Re: [Django] #6707: Another implementation for ReverseManyRelatedObjectsDescriptor.__set__ method

#6707: Another implementation for ReverseManyRelatedObjectsDescriptor.__set__ method -+- Reporter: favo |Owner: loic Type: Bug | Status:

Re: [Django] #22738: Schema migration: test_add_field_temp_default_boolean

#22738: Schema migration: test_add_field_temp_default_boolean -+- Reporter: maxi |Owner: nobody Type: | Status: new

Re: [Django] #22738: Schema migration: test_add_field_temp_default_boolean

#22738: Schema migration: test_add_field_temp_default_boolean -+- Reporter: maxi |Owner: nobody Type: | Status: closed

[django/django] dbdae3: Fixed #22738 -- Abstracted boolean field type intr...

Branch: refs/heads/master Home: https://github.com/django/django Commit: dbdae3a75512bddbf0b75ea6354fb3fc4bdb53cf https://github.com/django/django/commit/dbdae3a75512bddbf0b75ea6354fb3fc4bdb53cf Author: Claude Paroz Date: 2014-09-26 (Fri, 26 Sep 2014)

Re: [Django] #23543: Documentation how to test custom management command missing

#23543: Documentation how to test custom management command missing --+ Reporter: wittwerch |Owner: nobody Type: Cleanup/optimization | Status: new

[django/django] 458409: Silenced some deprecation warnings in contrib.site...

Branch: refs/heads/master Home: https://github.com/django/django Commit: 45840927d3516770be2654422e752357d5c063a5 https://github.com/django/django/commit/45840927d3516770be2654422e752357d5c063a5 Author: Loic Bistuer Date: 2014-09-27 (Sat, 27 Sep 2014)

Re: [Django] #22384: Deprecate the ability to reverse by dotted path

#22384: Deprecate the ability to reverse by dotted path -+- Reporter: timo |Owner: timo Type: | Status: closed Cleanup/optimization

Re: [Django] #22738: Schema migration: test_add_field_temp_default_boolean

#22738: Schema migration: test_add_field_temp_default_boolean -+- Reporter: maxi |Owner: nobody Type: | Status: new

[django/django] 735588: [1.7.x] Fixed #23560 -- Fixed MigrationWrite to ha...

Branch: refs/heads/stable/1.7.x Home: https://github.com/django/django Commit: 7355885ef504cc34f447311741511018f777667f https://github.com/django/django/commit/7355885ef504cc34f447311741511018f777667f Author: Loic Bistuer Date: 2014-09-27 (Sat, 27 Sep

Re: [Django] #23560: MigrationWriter prefixes builtin types with __builtins__.

#23560: MigrationWriter prefixes builtin types with __builtins__. +- Reporter: loic|Owner: nobody Type: Bug | Status: closed Component: Migrations |

[django/django] b23d47: Fixed #23560 -- Fixed MigrationWrite to handle bui...

Branch: refs/heads/master Home: https://github.com/django/django Commit: b23d47412c12352ba2e2133b05a15ccd09e81af3 https://github.com/django/django/commit/b23d47412c12352ba2e2133b05a15ccd09e81af3 Author: Loic Bistuer Date: 2014-09-27 (Sat, 27 Sep 2014)

Re: [Django] #23560: MigrationWriter prefixes builtin types with __builtins__.

#23560: MigrationWriter prefixes builtin types with __builtins__. +- Reporter: loic|Owner: nobody Type: Bug | Status: closed Component: Migrations |

[django/django]

Branch: refs/heads/ticket23560 Home: https://github.com/django/django -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[django/django] b23d47: Fixed #23560 -- Fixed MigrationWrite to handle bui...

Branch: refs/heads/ticket23560 Home: https://github.com/django/django Commit: b23d47412c12352ba2e2133b05a15ccd09e81af3 https://github.com/django/django/commit/b23d47412c12352ba2e2133b05a15ccd09e81af3 Author: Loic Bistuer Date: 2014-09-27 (Sat, 27 Sep

[django/django] 091289: [1.7.X] How many is two?

Branch: refs/heads/stable/1.7.x Home: https://github.com/django/django Commit: 091289d95039cfaa4a94cd40ac5055915f72971e https://github.com/django/django/commit/091289d95039cfaa4a94cd40ac5055915f72971e Author: Carl Meyer Date: 2014-09-26 (Fri, 26 Sep 2014)

[django/django] f5c932: How many is two?

Branch: refs/heads/master Home: https://github.com/django/django Commit: f5c932ddec8605df82319850d0f0e2f4dad1de11 https://github.com/django/django/commit/f5c932ddec8605df82319850d0f0e2f4dad1de11 Author: Carl Meyer Date: 2014-09-26 (Fri, 26 Sep 2014)

Re: [Django] #23561: Can unauthorized JS execution happen in quoted & escaped HTML class name?

#23561: Can unauthorized JS execution happen in quoted & escaped HTML class name? ---+ Reporter: djbug |Owner: nobody Type: Uncategorized | Status: closed

[django/django] d7bc30: [1.7.X] Fixed #23561 -- Corrected a security doc e...

Branch: refs/heads/stable/1.7.x Home: https://github.com/django/django Commit: d7bc30ffd26ebbe6d98fcd08d9120f44702d2a62 https://github.com/django/django/commit/d7bc30ffd26ebbe6d98fcd08d9120f44702d2a62 Author: Carl Meyer Date: 2014-09-26 (Fri, 26 Sep 2014)

Re: [Django] #23561: Can unauthorized JS execution happen in quoted & escaped HTML class name?

#23561: Can unauthorized JS execution happen in quoted & escaped HTML class name? ---+ Reporter: djbug |Owner: nobody Type: Uncategorized | Status: closed

[django/django] d16bc7: Fixed #23561 -- Corrected a security doc example t...

Branch: refs/heads/master Home: https://github.com/django/django Commit: d16bc7f0e46785bcf422310c41d20b25c0112051 https://github.com/django/django/commit/d16bc7f0e46785bcf422310c41d20b25c0112051 Author: Carl Meyer Date: 2014-09-26 (Fri, 26 Sep 2014)

Re: [Django] #23460: Allow a literal `%s` to be passed through extra select

#23460: Allow a literal `%s` to be passed through extra select -+- Reporter: mattrobenolt |Owner: nobody Type: Bug | Status: closed

[django/django] ef5f9b: Fixed #23460 -- Added literal `%s` support to extr...

Branch: refs/heads/master Home: https://github.com/django/django Commit: ef5f9b6ae8c873927aa6047f5f9d1d902a0c2177 https://github.com/django/django/commit/ef5f9b6ae8c873927aa6047f5f9d1d902a0c2177 Author: Matt Robenolt Date: 2014-09-26 (Fri, 26 Sep

Re: [Django] #23561: Can unauthorized JS execution happen in quoted & escaped HTML class name?

#23561: Can unauthorized JS execution happen in quoted & escaped HTML class name? ---+ Reporter: djbug |Owner: nobody Type: Uncategorized | Status: new Component:

Re: [Django] #23561: Can unauthorized JS execution happen in quoted & escaped HTML class name?

#23561: Can unauthorized JS execution happen in quoted & escaped HTML class name? ---+-- Reporter: djbug |Owner: nobody Type: Uncategorized | Status: new

Re: [Django] #23561: Can unauthorized JS execution happen in quoted & escaped HTML class name?

#23561: Can unauthorized JS execution happen in quoted & escaped HTML class name? ---+-- Reporter: djbug |Owner: nobody Type: Uncategorized | Status: new

[Django] #23561: Can unauthorized JS execution happen in quoted & escaped HTML class name?

#23561: Can unauthorized JS execution happen in quoted & escaped HTML class name? ---+ Reporter: djbug | Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |Version: 1.7

[django/django]

Branch: refs/heads/ticket23560 Home: https://github.com/django/django -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[django/django] ff40c4: Fixed #23560 -- Fixed MigrationWrite to handle bui...

Branch: refs/heads/ticket23560 Home: https://github.com/django/django Commit: ff40c4f36b6d4056dbf85a4b31fb275943aff4bb https://github.com/django/django/commit/ff40c4f36b6d4056dbf85a4b31fb275943aff4bb Author: Loic Bistuer Date: 2014-09-26 (Fri, 26 Sep

[django/django] 17557d: Fixed #8408 -- Added ModelAdmin.show_full_result_c...

Branch: refs/heads/master Home: https://github.com/django/django Commit: 17557d068c43bd61cdc6c18caf250ffa469414a1 https://github.com/django/django/commit/17557d068c43bd61cdc6c18caf250ffa469414a1 Author: Thomas Chaumeny Date: 2014-09-26 (Fri, 26

Re: [Django] #8408: Add a new meta option: don't do count(*) in admin

#8408: Add a new meta option: don't do count(*) in admin ---+- Reporter: lidaobing |Owner: tchaumeny Type: New feature| Status: closed Component: contrib.admin |

Re: [Django] #23559: Staff (not superusers) should not manage perms of Users

#23559: Staff (not superusers) should not manage perms of Users ---+ Reporter: Tuttle |Owner: nobody Type: New feature| Status: new Component: Documentation |

Re: [Django] #23426: migrations.RunSQL's function signature implies it won't do any parameter substitution

#23426: migrations.RunSQL's function signature implies it won't do any parameter substitution -+- Reporter: ris |Owner: Type: | Markush2010

Re: [Django] #23543: Documentation how to test custom management command missing

#23543: Documentation how to test custom management command missing --+ Reporter: wittwerch |Owner: nobody Type: Cleanup/optimization | Status: new

Re: [Django] #23543: Documentation how to test custom management command missing

#23543: Documentation how to test custom management command missing --+ Reporter: wittwerch |Owner: nobody Type: Cleanup/optimization | Status: new

Re: [Django] #23560: MigrationWriter prefixes builtin types with __builtins__.

#23560: MigrationWriter prefixes builtin types with __builtins__. +- Reporter: loic|Owner: nobody Type: Bug | Status: new Component: Migrations |

Re: [Django] #23560: MigrationWriter prefixes builtin types with __builtins__.

#23560: MigrationWriter prefixes builtin types with __builtins__. +-- Reporter: loic|Owner: nobody Type: Bug | Status: new Component: Migrations |

Re: [Django] #23460: Allow a literal `%s` to be passed through extra select

#23460: Allow a literal `%s` to be passed through extra select -+- Reporter: mattrobenolt |Owner: nobody Type: Bug | Status: new Component:

[Django] #23560: MigrationWriter prefixes builtin types with __builtins__.

#23560: MigrationWriter prefixes builtin types with __builtins__. --+ Reporter: loic| Owner: nobody Type: Bug | Status: new Component: Migrations |

Re: [Django] #23555: QuerySet.first suppresses internal IndexError exceptions

#23555: QuerySet.first suppresses internal IndexError exceptions -+- Reporter: artemrizhov |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #23559: Staff (not superusers) should not manage perms of Users

#23559: Staff (not superusers) should not manage perms of Users ---+ Reporter: Tuttle |Owner: nobody Type: New feature| Status: new Component: Documentation |

Re: [Django] #23556: Allow migrations to depend on a migration only part of a squashed migration

#23556: Allow migrations to depend on a migration only part of a squashed migration -+- Reporter: Markush2010 |Owner: Type: | Markush2010

[Django] #23559: Staff (not superusers) should not manage perms of Users

#23559: Staff (not superusers) should not manage perms of Users ---+ Reporter: Tuttle | Owner: nobody Type: New feature| Status: new Component: contrib.admin |Version: Severity: Normal |

Re: [Django] #23555: QuerySet.first suppresses internal IndexError exceptions

#23555: QuerySet.first suppresses internal IndexError exceptions -+- Reporter: artemrizhov |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #23556: Allow migrations to depend on a migration only part of a squashed migration

#23556: Allow migrations to depend on a migration only part of a squashed migration -+- Reporter: Markush2010 |Owner: Type: | Markush2010

[django/django] d1ca70: Factorized schema_editor() at BaseDatabaseWrapper ...

Branch: refs/heads/master Home: https://github.com/django/django Commit: d1ca70110f49f0be90206c8da516ac16aebc8c75 https://github.com/django/django/commit/d1ca70110f49f0be90206c8da516ac16aebc8c75 Author: Claude Paroz Date: 2014-09-26 (Fri, 26 Sep 2014)

Re: [Django] #22738: Schema migration: test_add_field_temp_default_boolean

#22738: Schema migration: test_add_field_temp_default_boolean --+ Reporter: maxi |Owner: nobody Type: Cleanup/optimization | Status: new Component: