Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

analytics_subscription_transitions: events START/STOP should have null prev/next respectively #12

Closed
kevinpostlewaite opened this issue Sep 24, 2013 · 0 comments
Closed

analytics_subscription_transitions: events START/STOP should have null prev/next respectively #12

kevinpostlewaite opened this issue Sep 24, 2013 · 0 comments
Assignees
@pierre
Labels
bug

Comments

@kevinpostlewaite
Copy link
Contributor

prev product should be null for START events but it's not always:
select * from analytics_subscription_transitions where event like 'START%' and prev_product_name is not null

next product should be null for STOP events but it's not always:
select * from analytics_subscription_transitions where event like 'STOP%' and prev_product_name is null
@ghost ghost assigned pierre Sep 25, 2013
@pierre pierre closed this as completed in 7b067d2 Sep 25, 2013
@pierre pierre mentioned this issue Sep 25, 2013
Closed
pierre pushed a commit that referenced this issue Sep 25, 2013
sanity: add queries for #3, #4 and #12
af190ef 
This closes #6.

Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pierre pierre

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pierre @kevinpostlewaite