django_tickets: tickets: 1 row where changetime = "2011-05-20 08:53:31" and "created" is on date 2008-08-13 sorted by has

1 row where changetime = "2011-05-20 08:53:31" and "created" is on date 2008-08-13 sorted by has_patch

descending

id	created	changetime	last_pulled_from_trac	stage	status	component	type	severity	version	resolution	summary	description	owner	reporter	keywords	easy	has_patch ▼	needs_better_patch	needs_tests	needs_docs	ui_ux
8281	2008-08-13 08:39:34	2011-05-20 08:53:31	2022-03-06 03:41:50.350073	Accepted	closed	HTTP handling	New feature	Normal	1.0-alpha	wontfix	Django running ounder PyISAPIe on IIS doesn't detect HTTPS	The is_secure() function in django.http.Request uses os.environ to detect whether or not the request is HTTPS or not. This doesn't work on Windows because the environment doesn't contain this information. PyISAPIe makes this information available in META (well, actually it doesn't yet, but that's another bug and patch to file against PyISAPIe). The Django patch is against django.http.__init__.py and the PyISAPIe patch is against django.core.handlers.pysiapi.py. We're using Django trunk r8066. Some [http://www.kirit.com/Blog:/2008-08-13/HTTPS%20detection%20in%20Django%20under%20PyISAPIe extra information is available on my blog].	nobody	KayEss	PyISAPIe HTTPS	0	1	1	0	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
    );