Re: [Django] #33552: has_key, has_keys, and has_any_keys JSONField() lookups don't handle numeric keys on SQLite, MySQL, and Oracle.

#33552: has_key, has_keys, and has_any_keys JSONField() lookups don't handle numeric keys on SQLite, MySQL, and Oracle. -+- Reporter: TheTerrasque |Owner: Sage

[Django] #33577: Confirm/Add support for GDAL 3.4.

#33577: Confirm/Add support for GDAL 3.4. -+- Reporter: Mariusz| Owner: Mariusz Felisiak Felisiak | Type: New| Status: assigned fe

Re: [Django] #33577: Confirm/Add support for GDAL 3.4.

#33577: Confirm/Add support for GDAL 3.4. -+- Reporter: Mariusz Felisiak |Owner: Mariusz | Felisiak Type: New feature | S

Re: [Django] #33577: Confirm/Add support for GDAL 3.4.

#33577: Confirm/Add support for GDAL 3.4. -+- Reporter: Mariusz Felisiak |Owner: Mariusz | Felisiak Type: New feature | S

Re: [Django] #33577: Confirm/Add support for GDAL 3.4.

#33577: Confirm/Add support for GDAL 3.4. -+- Reporter: Mariusz Felisiak |Owner: Mariusz | Felisiak Type: New feature | S

Re: [Django] #33256: Some schema tests don't clean up their tables

#33256: Some schema tests don't clean up their tables -+- Reporter: Tim Graham |Owner: Mohammad Type: | Ali Mehdizadeh Cleanup/optimization |

Re: [Django] #33256: Some schema tests don't clean up their tables

#33256: Some schema tests don't clean up their tables -+- Reporter: Tim Graham |Owner: Mohammad Type: | Ali Mehdizadeh Cleanup/optimization |

Re: [Django] #33256: Some schema tests don't clean up their tables

#33256: Some schema tests don't clean up their tables -+- Reporter: Tim Graham |Owner: Mohammad Type: | Ali Mehdizadeh Cleanup/optimization |

[Django] #33578: How feasible is modifying the django.db.connections object at run time for a multitenant system which uses isolated databases for tenancy

#33578: How feasible is modifying the django.db.connections object at run time for a multitenant system which uses isolated databases for tenancy -+- Reporter: mukilr | Owner: nobody

Re: [Django] #33578: How feasible is modifying the django.db.connections object at run time for a multitenant system which uses isolated databases for tenancy

#33578: How feasible is modifying the django.db.connections object at run time for a multitenant system which uses isolated databases for tenancy -+- Reporter: Mukil Rajeev |Owner: nobody

Re: [Django] #33578: How feasible is modifying the django.db.connections object at run time for a multitenant system which uses isolated databases for tenancy

#33578: How feasible is modifying the django.db.connections object at run time for a multitenant system which uses isolated databases for tenancy -+- Reporter: mukilr |Owner: nobody

Re: [Django] #33577: Confirm/Add support for GDAL 3.4.

#33577: Confirm/Add support for GDAL 3.4. -+- Reporter: Mariusz Felisiak |Owner: Mariusz | Felisiak Type: New feature | S

Re: [Django] #31169: Allow parallel test runner to work with Windows/macOS `spawn` process start method.

#31169: Allow parallel test runner to work with Windows/macOS `spawn` process start method. -+- Reporter: Brandon Navra|Owner: David | Smith Typ

Re: [Django] #33533: Should it be impossible for a session dict to return more than one value for a key?

#33533: Should it be impossible for a session dict to return more than one value for a key? --+-- Reporter: Michael |Owner: nobody Type: Uncategorized | Status:

Re: [Django] #33533: SESSION_SAVE_EVERY_REQUEST = True does not handle parallel requests well if some scenarios (was: Should it be impossible for a session dict to return more than one value for a key

#33533: SESSION_SAVE_EVERY_REQUEST = True does not handle parallel requests well if some scenarios --+-- Reporter: Michael |Owner: nobody Type: Uncategorized | S

Re: [Django] #33533: SESSION_SAVE_EVERY_REQUEST = True does not handle parallel requests well if some scenarios

#33533: SESSION_SAVE_EVERY_REQUEST = True does not handle parallel requests well if some scenarios --+-- Reporter: Michael |Owner: nobody Type: Uncategorized | S

[Django] #33579: Raise a specialized exception when Model.save(update_fields) does not affect any rows

#33579: Raise a specialized exception when Model.save(update_fields) does not affect any rows -+- Reporter: Simon | Owner: nobody Charette | Type: N

Re: [Django] #33579: Raise a specialized exception when Model.save(update_fields) does not affect any rows

#33579: Raise a specialized exception when Model.save(update_fields) does not affect any rows -+- Reporter: Simon Charette |Owner: nobody Type: New feature |