Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

As a developer, I'd like to refactor ActionableDynamicQuery to support customized tx boundaries setup and optimize the inefficient pagination logic

Description

None

Activity

Show:

Brian ChanSeptember 1, 2014 at 10:32 AM

Email from Marcellus:

Hey Brian,

I've sent to you a new ee-6.2-x pull request for containing the first commit of a previous https://github.com/brianchandotcom/liferay-portal-ee/pull/4910.

I know the full backport caused regressions on 6.2.x as described on https://issues.liferay.com/browse/BPR-528 but I just sent the TransactionInvoker classes with no impact on the portal.

I need this infrastructure to be able to use it on https://github.com/brianchandotcom/liferay-plugins-ee/pull/8586

Thanks

Brian ChanSeptember 1, 2014 at 10:32 AM

Lawrence LeeMay 13, 2014 at 3:17 PM

Closing ticket as completed stories with no front end element to be tested.

Brian ChanApril 15, 2014 at 2:54 PM

We decided to make it less aggressive by defaulting to the old behavior (same tx) and only using a new tx if you decide to.

See https://github.com/brianchandotcom/liferay-portal/commit/37f6e85bbfcac83286feda89f11f641e3e43318a

Brian ChiuApril 15, 2014 at 12:47 PM

I've reverted this in ee-6.2.x because it causes backend tests to fail. See for more details.

Completed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Branch Version/s

6.2.x

Backported to Branch

Committed

Git Pull Request

Components

Fix versions

Affects versions

Priority

Zendesk Support

Created April 9, 2014 at 12:26 PM
Updated June 26, 2023 at 6:11 AM
Resolved September 3, 2014 at 3:20 PM