3/29/2017 10:58:03 AM
the entity and the entity record id
both before and after executing the JDBC transaction.
In reality, because we want the latest state for the history tables,
we need to query for the current state before the JDBC transaction
only in case of DELETE operations.
Additionally, no need to retrieve the entity record id separately
(it comes for free from the entity).
This saves 3 JDBC calls for any CREATE or DELETE operation, 2 for any UPDATE operation.
Signed-off-by: Pierre-Alexandre Meyer <pierre@mouraf.org>
|
3/29/2017 8:10:46 AM
throws NullPointerException if the provided key is null.
Signed-off-by: Pierre-Alexandre Meyer <pierre@mouraf.org>
|
3/29/2017 8:07:24 AM
is in preparation of upcoming performance-related history and audit changes.
See also https://github.com/killbill/killbill/issues/335.
Signed-off-by: Pierre-Alexandre Meyer <pierre@mouraf.org>
|
|
|
3/28/2017 2:56:31 PM
Meyer <pierre@mouraf.org>
|
3/28/2017 4:33:18 PM
account creation call, the record isn't yet visible
outside the transaction: any call to ImmutableAccountInternalApi
to refresh the InternalCallContext would not only always
result in a cache miss, but also never result in finding the record
in the database.
Re-work the code to not issue any DB call. This saves us 4 DB queries
per account creation call.
Signed-off-by: Pierre-Alexandre Meyer <pierre@mouraf.org>
|
3/28/2017 4:08:22 AM
Pierre-Alexandre Meyer <pierre@mouraf.org>
|
|
|
3/27/2017 4:58:40 PM
out of order plan specifier during shopping card api
|
3/28/2017 3:10:46 AM
Pierre-Alexandre Meyer <pierre@mouraf.org>
|
