Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
entity system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Dec 2013 at 00:01 UTC
Updated:
29 Jul 2014 at 23:13 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
chx commentedAssigning to tim.plunkett for review.
Comment #2
chx commentedIt'd be nice to explore injecting the entity query object in a followup. Config entities already do it.
Comment #4
chx commentedComment #5
dawehnerGood work. This allows for potential performance optimized entity query implementations to use it.
Comment #6
damiankloip commentedComment #7
damiankloip commentedLooks good to me too.
Only thing is we might want to put the call to entityQuery() in a wrapper function? But prob don't need this now, only when/if this class gets a dedicated unit test or something.
Also, spotted a really minor issue in the ConfigEntityUnitTest, so filed a small followup for that: #2158299: ConfigEntityUnitTest does not check properties on all loaded entities
Comment #8
chx commentedThe call to entityQuery will go away when I will convert all the classes to receive the query factory via injection as config already does.
Comment #9
webchickCommitted and pushed to 8.x. Thanks!
Comment #10
yched commentedWould there be a way to optimize Config EFQ so that it doesn't load and loop over all config entries when the query has conditions on 'id' ?
[edit: patch at #2163919: Optimise Config EntityQueries in case there are conditions on the 'id' ]