django_tickets: tickets: 3 rows where "created" is on date 2008-08-14 and resolution = "duplicate" sorted by resolution

3 rows where "created" is on date 2008-08-14 and resolution = "duplicate" sorted by resolution

descending

id	created	changetime	last_pulled_from_trac	stage	status	component	version	resolution ▼	summary	description	owner	reporter	keywords	has_patch	needs_better_patch
8302	2008-08-14 03:26:19	2008-08-14 03:31:14	2022-03-06 03:41:53.539158	Unreviewed	closed	Documentation	dev	duplicate	Documentation type-o in "Order of Middleware_Classes"	http://www.djangoproject.com/documentation/cache/#order-of-middleware-classes Look at the last word in this copy/paste: "Order of MIDDLEWARE_CLASSES If you use caching middlewaare, . . ."	nobody	defcube		0	0
8318	2008-08-14 17:39:57	2011-09-28 16:12:17	2022-03-06 03:41:56.194187	Unreviewed	closed	Database layer (models, ORM)	dev	duplicate	Unexpected behavior with ManyRelatedManager get_or_create()	I've noticed 2 things happening when using a ManyRelatedManager get_or_create method: 1. The new related object is created but not added to the current object. Looking at django/db/models/fields/related.py, get_or_create is not overridden() in the ManyRelatedManager definition, but create() is to add the new object. 2. Using get_or_create() to add a new object that already exists regardless of whether or not it's linked to the current object results in a related object DoesNotExist exception. {{{ from django.db import models class Controller(models.Model): name = models.CharField(max_length=30, unique=True) def __unicode__(self): return self.name class ControllerGroup(models.Model): name = models.CharField(max_length=30, unique=True) controllers = models.ManyToManyField(Controller) def __unicode__(self): return self.name # create a controller >>> c1 = Controller(name='controller1').save() # create a controller group >>> cg = ControllerGroup(name='my group').save() # 'add' using get_or_create() >>> cg.controllers.get_or_create(name='controller1') Traceback (most recent call last): File "<console>", line 1, in <module> File "/usr/local/django/src/trunk/django/db/models/manager.py", line 84, in get_or_create return self.get_query_set().get_or_create(kwargs) File "/usr/local/django/src/trunk/django/db/models/query.py", line 335, in get_or_create return self.get(kwargs), False File "/usr/local/django/src/trunk/django/db/models/query.py", line 300, in get % self.model._meta.object_name) DoesNotExist: Controller matching query does not exist. # trying 'adding' a controller that doesn't exist >>> cg.controllers.get_or_create(name='controller2') (<Controller: controller2>, True) # looks like it's been added, let's check >>> cg.controllers.all() [] }}}	nobody	fredbartle	many related manager get_or_create	1	1
8323	2008-08-14 19:31:07	2011-01-18 23:20:32	2022-03-06 03:41:56.985519	Design decision needed	closed	contrib.localflavor	dev	duplicate	British local flavor package named inconsistently	I just noticed that according to the [http://www.djangoproject.com/documentation/localflavor/ local flavor documentation], the packages are named using the [http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm ISO 3166 country codes]. However, at present, the British local flavor is within a package called "uk" (United Kingdom) rather than "gb" (Great Britain), which would seem to be the correct 2 letter code. This is a pretty minor issue as no other country has been assigned "uk" as a country code at this time. For consistency, we may want to rename the package to "gb". If so, this should probably be done prior to 1.0 to avoid compatibility issues in the future. If it is decided that the name should be left as is, then I think the documentation should at least be updated to mention this legacy naming anomaly. All the other local flavors appear to be using the correct ISO codes.	nobody	frasern		0	0

Advanced export

JSON shape: default, array, newline-delimited, object

CREATE TABLE tickets (
        id int primary key,
        created datetime,
        changetime datetime,
        last_pulled_from_trac datetime,
        stage text,
        status text,
        component text,
        type text,
        severity text,
        version text,
        resolution text,
        summary text,
        description text,
        owner text,
        reporter text,
        keywords text,
        easy boolean,
        has_patch boolean,
        needs_better_patch boolean,
        needs_tests boolean,
        needs_docs boolean,
        ui_ux boolean
    );