Re: [Django] #29082: Make the test client automatically encode JSON data

#29082: Make the test client automatically encode JSON data --+ Reporter: Nick |Owner: nobody Type: Cleanup/optimization | Status: new Component:

Re: [Django] #7835: Provide the ability for model definitions that are only availably during testing

#7835: Provide the ability for model definitions that are only availably during testing -+ Reporter: Russell Keith-Magee |Owner: nobody Type: New feature |

Re: [Django] #7835: Provide the ability for model definitions that are only availably during testing

#7835: Provide the ability for model definitions that are only availably during testing -+ Reporter: Russell Keith-Magee |Owner: nobody Type: New feature |

[Django] #29088: Fail to perform a json lookup field search using __in syntax

#29088: Fail to perform a json lookup field search using __in syntax -+ Reporter: daavelino | Owner: nobody Type: Uncategorized | Status: new Component:

Re: [Django] #29086: Bytestrings on CharFields getting saved as "b'data'"

#29086: Bytestrings on CharFields getting saved as "b'data'" -+- Reporter: Collin Anderson |Owner: nobody Type: Bug | Status: new Component:

[Django] #29087: Impossible to delete pending new inline in admin when invalid (delete button missing)

#29087: Impossible to delete pending new inline in admin when invalid (delete button missing) -+ Reporter: Owen Heisler | Owner: nobody Type: Bug| Status: new

Re: [Django] #29076: Make Model.refresh_from_db() clear cached foreign key and one to one fields, even if the related ID hasn't changed

#29076: Make Model.refresh_from_db() clear cached foreign key and one to one fields, even if the related ID hasn't changed -+- Reporter: Jon Dufresne |Owner: nobody Type: New

Re: [Django] #29086: Bytestrings on CharFields getting saved as "b'data'"

#29086: Bytestrings on CharFields getting saved as "b'data'" -+- Reporter: Collin Anderson |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #29086: Bytestrings on CharFields getting saved as "b'data'"

#29086: Bytestrings on CharFields getting saved as "b'data'" -+- Reporter: Collin Anderson |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #29086: Bytestrings on CharFields getting saved as "b'data'"

#29086: Bytestrings on CharFields getting saved as "b'data'" -+- Reporter: Collin Anderson |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #29086: Bytestrings on CharFields getting saved as "b'data'"

#29086: Bytestrings on CharFields getting saved as "b'data'" -+- Reporter: Collin Anderson |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #29086: Bytestrings on CharFields getting saved as "b'data'"

#29086: Bytestrings on CharFields getting saved as "b'data'" -+- Reporter: Collin Anderson |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #29086: Bytestrings on CharFields getting saved as "b'data'"

#29086: Bytestrings on CharFields getting saved as "b'data'" -+- Reporter: Collin Anderson |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #29086: Bytestrings on CharFields getting saved as "b'data'"

#29086: Bytestrings on CharFields getting saved as "b'data'" -+- Reporter: Collin Anderson |Owner: nobody Type: Bug | Status: new Component:

[Django] #29086: Bytestrings on CharFields getting saved as "b'data'"

#29086: Bytestrings on CharFields getting saved as "b'data'" -+- Reporter: Collin | Owner: nobody Anderson | Type: Bug| Status: new

Re: [Django] #29075: Wrong version in settings.py comments

#29075: Wrong version in settings.py comments +-- Reporter: Vedran Karačić |Owner: nobody Type: Uncategorized | Status: closed Component: Documentation |

Re: [Django] #29079: Django settings should not cache user wrapped settings

#29079: Django settings should not cache user wrapped settings -+- Reporter: Riccardo Di |Owner: nobody Virgilio | Type: Uncategorized|

Re: [Django] #29084: Skip postgres_tests's SimpleSearchTest's that require 'english_stem' configuration if the machine's configuration is different

#29084: Skip postgres_tests's SimpleSearchTest's that require 'english_stem' configuration if the machine's configuration is different -+- Reporter: Дилян Палаузов |Owner: (none) Type:

Re: [Django] #29084: Skip postgres_tests's SimpleSearchTest's that require 'english_stem' configuration if the machine's configuration is different

#29084: Skip postgres_tests's SimpleSearchTest's that require 'english_stem' configuration if the machine's configuration is different -+- Reporter: Дилян Палаузов |Owner: (none) Type:

Re: [Django] #29084: Skip postgres_tests's SimpleSearchTest's that require 'english_stem' configuration if the machine's configuration is different

#29084: Skip postgres_tests's SimpleSearchTest's that require 'english_stem' configuration if the machine's configuration is different -+- Reporter: Дилян Палаузов |Owner: (none) Type:

Re: [Django] #29085: Possible data loss on .save() with unsaved related model

#29085: Possible data loss on .save() with unsaved related model -+- Reporter: Jonas Haag |Owner: nobody Type: | Status: new

Re: [Django] #29069: Static file serving does not call request_finished signal

#29069: Static file serving does not call request_finished signal -+- Reporter: André Cruz |Owner: nobody Type: Bug | Status: new

Re: [Django] #29084: Skip postgres_tests's SimpleSearchTest's that require 'english_stem' configuration if the machine's configuration is different (was: tests.postgres_tests.test_search.SimpleSearchT

#29084: Skip postgres_tests's SimpleSearchTest's that require 'english_stem' configuration if the machine's configuration is different -+- Reporter: Дилян Палаузов |Owner: (none) Type:

[Django] #29085: Possible data loss on .save() with unsaved related model

#29085: Possible data loss on .save() with unsaved related model -+- Reporter: Jonas | Owner: nobody Haag | Type: | Status:

Re: [Django] #29085: Possible data loss on .save() with unsaved related model

#29085: Possible data loss on .save() with unsaved related model -+- Reporter: Jonas Haag |Owner: nobody Type: | Status: new

Re: [Django] #29084: tests.postgres_tests.test_search.SimpleSearchTest: to_tsvector/plainto_tsquery need 'english' as first parameter

#29084: tests.postgres_tests.test_search.SimpleSearchTest: to_tsvector/plainto_tsquery need 'english' as first parameter -+- Reporter: Дилян Палаузов |Owner: (none) Type:

Re: [Django] #29084: tests.postgres_tests.test_search.SimpleSearchTest: to_tsvector/plainto_tsquery need 'english' as first parameter

#29084: tests.postgres_tests.test_search.SimpleSearchTest: to_tsvector/plainto_tsquery need 'english' as first parameter -+- Reporter: Дилян Палаузов |Owner: (none) Type:

Re: [Django] #29036: HTML5 required validation does not work for SelectDateWidget

#29036: HTML5 required validation does not work for SelectDateWidget +-- Reporter: Vlastimil Zíma |Owner: nobody Type: Bug | Status: closed Component: Forms

Re: [Django] #29036: HTML5 required validation for SelectDateWidget doesn't work if the attribute is added by JavaScript (was: HTML5 required validation does not work for SelectDateWidget)

#29036: HTML5 required validation for SelectDateWidget doesn't work if the attribute is added by JavaScript + Reporter: Vlastimil Zíma |Owner: nobody Type: Bug |

Re: [Django] #29076: Make Model.refresh_from_db() clear cached foreign key and one to one fields, even if the related ID hasn't changed (was: Model.refresh_from_db() should clear cached foreign key an

#29076: Make Model.refresh_from_db() clear cached foreign key and one to one fields, even if the related ID hasn't changed -+- Reporter: Jon Dufresne |Owner: nobody Type: New

Re: [Django] #29082: Make the test client automatically encode JSON data

#29082: Make the test client automatically encode JSON data --+ Reporter: Nick |Owner: nobody Type: Cleanup/optimization | Status: new Component:

Re: [Django] #29082: Make the test client automatically encode JSON data

#29082: Make the test client automatically encode JSON data --+ Reporter: Nick |Owner: nobody Type: Cleanup/optimization | Status: new Component:

Re: [Django] #29082: Make the test client automatically encode JSON data (was: force_bytes from utils.encoding.py produces invalid JSON for RequestFactory)

#29082: Make the test client automatically encode JSON data --+ Reporter: Nick |Owner: nobody Type: Cleanup/optimization | Status: new Component:

Re: [Django] #29081: Clarify QuerySet.select_related() example regarding "hitting the database"

#29081: Clarify QuerySet.select_related() example regarding "hitting the database" --+ Reporter: Дилян Палаузов|Owner: nobody Type: Cleanup/optimization |

Re: [Django] #29081: Clarify QuerySet.select_related() example regarding "hitting the database"

#29081: Clarify QuerySet.select_related() example regarding "hitting the database" --+ Reporter: Дилян Палаузов|Owner: nobody Type: Cleanup/optimization |

Re: [Django] #29035: Django Admin does not URL encode the search terms of list filters, breaking the search URL.

#29035: Django Admin does not URL encode the search terms of list filters, breaking the search URL. ---+-- Reporter: Nolan Love |Owner: nobody Type: Bug| Status:

Re: [Django] #29082: force_bytes from utils.encoding.py produces invalid JSON for RequestFactory

#29082: force_bytes from utils.encoding.py produces invalid JSON for RequestFactory ---+-- Reporter: Nick |Owner: nobody Type: Bug| Status: new Component:

Re: [Django] #29082: force_bytes from utils.encoding.py produces invalid JSON for RequestFactory

#29082: force_bytes from utils.encoding.py produces invalid JSON for RequestFactory ---+-- Reporter: Nick |Owner: nobody Type: Bug| Status: new Component:

Re: [Django] #29049: Add slicing notation to F expressions

#29049: Add slicing notation to F expressions -+- Reporter: Matthew Pava |Owner: nobody Type: New feature | Status: new Component: Database layer

[Django] #29084: tests.postgres_tests.test_search.SimpleSearchTest: to_tsvector/plainto_tsquery need 'english' as first parameter

#29084: tests.postgres_tests.test_search.SimpleSearchTest: to_tsvector/plainto_tsquery need 'english' as first parameter -+- Reporter: Дилян | Owner: (none) Палаузов |

Re: [Django] #29081: Clarify QuerySet.select_related() example regarding "hitting the database" (was: select_related and hitting the database)

#29081: Clarify QuerySet.select_related() example regarding "hitting the database" --+ Reporter: Дилян Палаузов|Owner: nobody Type: Cleanup/optimization |

Re: [Django] #29082: force_bytes from utils.encoding.py produces invalid JSON for RequestFactory

#29082: force_bytes from utils.encoding.py produces invalid JSON for RequestFactory ---+-- Reporter: Nick |Owner: nobody Type: Bug| Status: new Component:

Re: [Django] #29083: DateField returning string instead of date object (was: DateField() returning string instead of date object)

#29083: DateField returning string instead of date object -+- Reporter: Gary Aleixo |Owner: nobody Type: Bug | Status: closed Component:

Re: [Django] #29082: force_bytes from utils.encoding.py produces invalid JSON for RequestFactory

#29082: force_bytes from utils.encoding.py produces invalid JSON for RequestFactory ---+-- Reporter: Nick |Owner: nobody Type: Bug| Status: new Component:

[Django] #29083: DateField() returning string instead of date object

#29083: DateField() returning string instead of date object -+--- Reporter: Gary Aleixo| Owner: nobody Type: Bug| Status: new Component:

Re: [Django] #29033: Sitemap framework does not properly detect secure requests

#29033: Sitemap framework does not properly detect secure requests --+-- Reporter: Matt Magin|Owner: nobody Type: Bug | Status: closed Component:

Re: [Django] #29082: force_bytes from utils.encoding.py produces invalid JSON for RequestFactory

#29082: force_bytes from utils.encoding.py produces invalid JSON for RequestFactory ---+-- Reporter: Nick |Owner: nobody Type: Bug| Status: new Component:

Re: [Django] #29077: [Help] Why JSONField for MySql/MariaDB etc are not supported in Django?

#29077: [Help] Why JSONField for MySql/MariaDB etc are not supported in Django? +-- Reporter: Akhil Lawrence |Owner: nobody Type: Uncategorized | Status: closed

Re: [Django] #29082: force_bytes from utils.encoding.py produces invalid JSON for RequestFactory

#29082: force_bytes from utils.encoding.py produces invalid JSON for RequestFactory ---+-- Reporter: Nick |Owner: nobody Type: Bug| Status: new Component:

Re: [Django] #29082: force_bytes from utils.encoding.py produces invalid JSON for RequestFactory

#29082: force_bytes from utils.encoding.py produces invalid JSON for RequestFactory ---+-- Reporter: Nick |Owner: nobody Type: Bug| Status: new Component:

Re: [Django] #29080: SELECT @@SQL_AUTO_IS_NULL query for every page

#29080: SELECT @@SQL_AUTO_IS_NULL query for every page -+- Reporter: Nikos Katsos |Owner: nobody Type: | Status: closed

[Django] #29082: force_bytes from utils.encoding.py produces invalid JSON for RequestFactory

#29082: force_bytes from utils.encoding.py produces invalid JSON for RequestFactory --+ Reporter: Nick| Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #29079: Django settings should not cache user wrapped settings

#29079: Django settings should not cache user wrapped settings -+- Reporter: Riccardo Di |Owner: nobody Virgilio | Type: Uncategorized|

Re: [Django] #28668: Add ON CONFLICT support to QuerySet.bulk_create() (was: Add support for ON CONFLICT to bulk_create)

#28668: Add ON CONFLICT support to QuerySet.bulk_create() -+- Reporter: Tom Forbes |Owner: Tom | Forbes Type: New feature |

Re: [Django] #28668: Add ON CONFLICT support to QuerySet.bulk_create()

#28668: Add ON CONFLICT support to QuerySet.bulk_create() -+- Reporter: Tom Forbes |Owner: Tom | Forbes Type: New feature |

Re: [Django] #29081: select_related and hitting the database

#29081: select_related and hitting the database -+- Reporter: Дилян Палаузов |Owner: nobody Type: | Status: new Cleanup/optimization

[Django] #29081: select_related and hitting the database

#29081: select_related and hitting the database -+- Reporter: Дилян | Owner: nobody Палаузов | Type: | Status: new

Re: [Django] #29062: "database table locked errors" when using sqlite in-memory database with LiveServerTestCase

#29062: "database table locked errors" when using sqlite in-memory database with LiveServerTestCase -+- Reporter: Juozas Masiulis |Owner: nobody Type: Bug |

Re: [Django] #29062: "database table locked errors" when using sqlite in-memory database with LiveServerTestCase

#29062: "database table locked errors" when using sqlite in-memory database with LiveServerTestCase -+- Reporter: Juozas Masiulis |Owner: nobody Type: Bug |

[Django] #29080: SELECT @@SQL_AUTO_IS_NULL query for every page

#29080: SELECT @@SQL_AUTO_IS_NULL query for every page -+- Reporter: Nikos | Owner: nobody Katsos | Type: | Status: new

[Django] #29079: Django settings should not cache user wrapped settings

#29079: Django settings should not cache user wrapped settings + Reporter: Riccardo Di Virgilio | Owner: nobody Type: Uncategorized | Status: new

Re: [Django] #29066: Sum does not support __neg__

#29066: Sum does not support __neg__ -+- Reporter: Matthew Pava |Owner: Priyansh | Saxena Type: Bug |