Re: [Django] #22089: Deleting object with custom primary_key causes the pk to be None

#22089: Deleting object with custom primary_key causes the pk to be None -+- Reporter: anonymous|Owner: nobody Type: Uncategorized| Status: closed

Re: [Django] #22089: Deleting object with custom primary_key causes the pk to be None

#22089: Deleting object with custom primary_key causes the pk to be None -+- Reporter: anonymous|Owner: nobody Type: Uncategorized| Status: closed

Re: [Django] #22089: Deleting object with custom primary_key causes the pk to be None

#22089: Deleting object with custom primary_key causes the pk to be None -+- Reporter: anonymous|Owner: nobody Type: Uncategorized| Status: new Com

Re: [Django] #30934: django.db.backends logging output should include the database alias

#30934: django.db.backends logging output should include the database alias -+- Reporter: David Winterbottom |Owner: nobody Type: New feature | Status: new

Re: [Django] #31128: Custom template tags raise TemplateSyntaxError when keyword-only arguments with defaults are provided.

#31128: Custom template tags raise TemplateSyntaxError when keyword-only arguments with defaults are provided. -+-- Reporter: P-Seebauer |Owner: P-Seebauer Type: Bug |

Re: [Django] #31128: Custom template tags raise TemplateSyntaxError when keyword-only arguments with defaults are provided. (was: Bug in simple and inclusion tag parsing.)

#31128: Custom template tags raise TemplateSyntaxError when keyword-only arguments with defaults are provided. -+-- Reporter: P-Seebauer |Owner: P-Seebauer Type: Bug |

Re: [Django] #31117: ThreadTests fails due to double test_ prefix caused by TestDbCreationTests.

#31117: ThreadTests fails due to double test_ prefix caused by TestDbCreationTests. -+- Reporter: Matthijs Kooijman|Owner: Matthijs | Kooijman Type:

Re: [Django] #31055: Omits test_ prefix from database name when running subset of tests

#31055: Omits test_ prefix from database name when running subset of tests -+- Reporter: Matthijs Kooijman|Owner: Simon | Charette Type: Bug

Re: [Django] #31097: StringAgg And ArrayAgg with filtering in subquery generates invalid string_agg() SQL function call

#31097: StringAgg And ArrayAgg with filtering in subquery generates invalid string_agg() SQL function call -+- Reporter: Laurent Tramoy |Owner: David | Wobr

Re: [Django] #31097: StringAgg And ArrayAgg with filtering in subquery generates invalid string_agg() SQL function call

#31097: StringAgg And ArrayAgg with filtering in subquery generates invalid string_agg() SQL function call -+- Reporter: Laurent Tramoy |Owner: David | Wobr

Re: [Django] #30780: Make "Getting Help" documentation much more prominent.

#30780: Make "Getting Help" documentation much more prominent. -+- Reporter: Shai Berger |Owner: Gabriel Type: | Augendre Cleanup/optimization

Re: [Django] #30780: Make "Getting Help" documentation much more prominent.

#30780: Make "Getting Help" documentation much more prominent. -+- Reporter: Shai Berger |Owner: Gabriel Type: | Augendre Cleanup/optimization

Re: [Django] #30780: Make "Getting Help" documentation much more prominent.

#30780: Make "Getting Help" documentation much more prominent. -+- Reporter: Shai Berger |Owner: Gabriel Type: | Augendre Cleanup/optimization

Re: [Django] #30780: Make "Getting Help" documentation much more prominent.

#30780: Make "Getting Help" documentation much more prominent. -+- Reporter: Shai Berger |Owner: Gabriel Type: | Augendre Cleanup/optimization