refactor burnup SQL for consistency across different projects
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	• JAufrecht
	Aug 28 2015, 5:29 PM

Description

figure out best way to pass in a variable
rewrite all non-VE SQL to conform
- handle custom reconstruction SQL
- handle generic queries

Status	Assigned	Task
Resolved	• JAufrecht	T99958 [EPIC] Five teams sample their maintenance fraction and two teams track it throughout the quarter
Resolved	• ksmith	T110551 Generate Discovery burnup and maintenance fraction charts
Resolved	• JAufrecht	T107482 Create third version of VE burnup report
Resolved	MBinder_WMF	T108280 Create Mobile burnups
Resolved	• JAufrecht	T110705 refactor burnup SQL for consistency across different projects

• JAufrecht claimed this task.

• JAufrecht raised the priority of this task from to Medium.

• JAufrecht updated the task description. (Show Details)

Jdforrester-WMF edited a custom field.

• ggellerman lowered the priority of this task from Medium to Low.Sep 30 2015, 6:04 PM

• ggellerman edited a custom field.

Brainstorm:

call all SQL and R directly from Python
- easiest for looping and passing variables
- what is the best way to pass variables to SQL
  - command line to PSQL files
  - within the cursor
    - to PSQL files (current method)
    - to PLPGSQL stored procedures
      - this is probably best way to eliminate duplication.
use kwargs to pass everything to phlogiston subroutines (which maybe are in other files?)