Problem/Motivation

We currently do the join from the revision data table to the revision table the wrong way round

Proposed resolution

Fix it + write some tests.

Remaining tasks

Commit it

User interface changes

API changes

Data model changes

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dawehner created an issue. See original summary.

dawehner’s picture

Status: Active » Needs review
FileSize
3.57 KB

There we go.

dawehner’s picture

This time with more files.

jibran’s picture

Status: Needs review » Reviewed & tested by the community

Looks good to me. Test explains it all. Maybe before and after query of the test view and test only path would also help committers to understand the problem.

dawehner’s picture

Looks good to me. Test explains it all. Maybe before and after query of the test view and test only path would also help committers to understand the problem.

You mean completely broken vs. runnable?

jibran’s picture

You mean completely broken vs. runnable?

I just read #2626166-22: Create a view for content revisions and tested #2626166-28: Create a view for content revisions. Now I know what you mean so never mind me. This will also be usable for #1863906: [PP-1] Replace content revision table with a view so marking it as a major.

dawehner’s picture

Issue summary: View changes

Added a remaining task :)

alexpott’s picture

Status: Reviewed & tested by the community » Needs work

Do we need an empty update hook to force a cache clear? So that sites can the new views data?

dawehner’s picture

Yeah I think we totally could. Do we need to test this update then as well?

dawehner’s picture

Status: Needs work » Needs review
FileSize
7.68 KB
472 bytes

There we go. I'm not entirely convinced that we need a test for an empty update function

jibran’s picture

Status: Needs review » Reviewed & tested by the community

Thanks.

Status: Reviewed & tested by the community » Needs work

The last submitted patch, 10: 2630886-10.patch, failed testing.

dawehner’s picture

Status: Needs work » Reviewed & tested by the community

Random bot fluctuation

Status: Reviewed & tested by the community » Needs work

The last submitted patch, 10: 2630886-10.patch, failed testing.

The last submitted patch, 10: 2630886-10.patch, failed testing.

dawehner’s picture

Status: Needs work » Needs review

.

jibran’s picture

Status: Needs review » Reviewed & tested by the community

Still RTBC.

jibran’s picture

Still RTBC.

alexpott’s picture

Status: Reviewed & tested by the community » Needs work
+++ b/core/modules/views/views.install
@@ -329,5 +329,12 @@ function views_update_8003() {
 /**
+ * Clear caches due to updated entity views data.
+ */
+function views_update_8004() {
+  // Empty update to cause a cache flush so that views data is rebuilt.
+}
+
+/**
  * @} End of "addtogroup updates-8.0.0-rc".
  */

Yep we don't need a test for a cache clear but we need an new update group... 8.0.0-rc is history :)

We've been saying that anything with an update hook should be 8.1.x but I think this is an exception since it is a bug fix with an empty update hook - therefore I think we should put it in updates-8.0.x

dawehner’s picture

Status: Needs work » Needs review
FileSize
7.78 KB
598 bytes

Sure, there we go.

xjm’s picture

Issue tags: +Triaged core major

The core committers and Views maintainers (alexpott, xjm, effulgentsia, tim.plunkett, and dawehner) agreed that this is a major issue.

jibran’s picture

Status: Needs review » Reviewed & tested by the community
+++ b/core/modules/views/views.install
@@ -329,6 +329,15 @@ function views_update_8003() {
+ * @addtogroup updates-8.0.4

@@ -336,5 +345,5 @@ function views_update_8004() {
+ * @} End of "addtogroup updates-8.0.4".

I think @alexpott can decide whether to use 8.0.x or 8.0.4. Other then this is RTBC.

catch’s picture

Status: Reviewed & tested by the community » Fixed

8.0.x is good - there's no guarantee this gets released as part of 8.0.4 since that could be a security release, then it'd end up being 8.0.5 - also an update defgroup every six months is plenty.

Committed/pushed to 8.1.x and cherry-picked to 8.0.x. Thanks!

  • catch committed f9930b4 on 8.0.x
    Issue #2630886 by dawehner: Correct the join from revision data table to...
catch’s picture

  • catch committed 8bd5ae4 on 8.1.x
    Issue #2630886 by dawehner: Correct the join from revision data table to...
  • catch committed d5f4e3b on 8.1.x
    Issue #2630886 by dawehner: Correct the join from revision data table to...
jibran’s picture

Status: Fixed » Reviewed & tested by the community

@catch you only committed http://cgit.drupalcode.org/drupal/commit/?id=f9930b4 to 8.0.x instead of whole patch.

Status: Reviewed & tested by the community » Needs work

The last submitted patch, 20: 2630886-20.patch, failed testing.

jibran’s picture

Status: Needs work » Reviewed & tested by the community

Still RTBC. We need to revert #24 and commit #20 to 8.0.x

  • catch committed 080038f on 8.0.x
    Issue #2630886 by dawehner: Correct the join from revision data table to...
  • catch committed f30b7b0 on 8.0.x
    Revert "Issue #2630886 by dawehner: Correct the join from revision data...
catch’s picture

Status: Reviewed & tested by the community » Fixed

Arrgh. Thanks jibran. Reverted the bad commit and re-committed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.