7/2/2012 6:43:18 PM
acb999c429d343e863ce401623ec8686641266ac.
We're going to take a trigger approach and change Analytics to handle
it.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
7/2/2012 6:41:03 PM
pass yet.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
6/29/2012 9:01:42 PM
transitions, make sure the previous subscription is always
null.
Also, move all the dao logic into the transaction.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
6/29/2012 8:55:19 PM
Pierre-Alexandre Meyer <pierre@ning.com>
|
6/29/2012 8:43:44 PM
sure not to duplicate events in Analytics: requested phase events
and effective system phase events go in pair.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
6/29/2012 7:37:55 PM
Pierre-Alexandre Meyer <pierre@ning.com>
|
6/29/2012 7:37:26 PM
Pierre-Alexandre Meyer <pierre@ning.com>
|
6/29/2012 7:29:38 PM
commit 7634ba410e437337d00e38d2e622b4057fdca364.
We actually already store the subscription_id in the prev/next objects.
Although it makes sense in the Java code to have subscription_id in the
BusinessSubscription object, it feels weird to have it duplicated in the
table (prev/next). But let's keep it for now.
Conflicts:
analytics/src/main/java/com/ning/billing/analytics/BusinessSubscriptionTransitionRecorder.java
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
6/29/2012 7:06:50 PM
issues, we may now need to update transitions in bst.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
6/29/2012 6:24:41 PM
to handle future events.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
