1/24/2017 5:53:34 AM
triggered when limit == 1 and offset == -1.
In that case, exact match queries only are performed and the first result is returned.
This is to optimize the case when the user knows the email or name for example.
Signed-off-by: Pierre-Alexandre Meyer <pierre@mouraf.org>
|
|
|
1/23/2017 9:01:04 AM
listing API now pages through all payments, instead of going plugin by plugin.
This allows us to use the optimization from 8aabb264962263a30d2df4db34daaef3b135c59e
and also makes the results ordering less confusing (natural ordering instead of per plugin name).
The search API will also now optimize the search to query by state name only, if the search key looks like a state name.
One caveat is that the API will now miss payments with an external key that looks like a state name (e.g. paymentKey_ERRORED).
Signed-off-by: Pierre-Alexandre Meyer <pierre@mouraf.org>
|
1/23/2017 8:14:47 AM
only, to avoid retrieving full records which will be discarded anyways.
Signed-off-by: Pierre-Alexandre Meyer <pierre@mouraf.org>
|
1/23/2017 5:42:35 PM
create `SubscriptionBundle`. See #684
Also add logic in EntitlementApi#createBaseEntitlementsWithAddOns to behave in a similar way we do in EntitlementApi#createBaseEntitlement
with regard to unicity of bundle externalKey
|
|
|
|
|
1/20/2017 10:55:48 PM
catalog initialization. See #696
|
|
|
1/20/2017 9:24:42 PM
current separator when exporting data is the ',' so our import script does not understand the difference between
a value separated from another value versus values that contain JSON (and therefore ',' as well). Using a completely different
(unused) symbol makes the process of importing much simpler (and reliable)
import script has been changed accordingly to now handle the new '|' separator and i verifed notifications and bus_history tables are now correctly imported.
|
