 A fencing area question.
 Moral justification for “sheaf=continuously variable set” and local injectivity
 Getting the envelope of a family of curves
 $\int_{0}^{a+bi}\cos(z^2)\,dz\leq(a^2+b^2)^{1/2}\sinh(2ab)/(2ab)$
 Inverse image of a polynomial in two variables is simplyconnected?
 ChernSimons form on a 5d manifold
 Is there always a partition into distinct divisors of an abundant number involving the largest nontrivial divisor?
 Fourier Transform of Heat Equation with a Source
 Are these estimators consistent?
 Using +  * / operators and 4 4 4 4 digits find all formulas that would resolve to 1 2 3 4 5 6 7 8 9 10
 Fenchel's Problems, domain of inf function
 Differentiating p totally wrt y
 Write the general solution of a Schrödinger time independent equation for a Region by $\frac{1}{2}
 incompressible fluid flow between two fixed concentric cylinders
 Move centerpoint of sphere along an axis such that it contacts a plane at a point
 The frustum equations; how much can you tilt a frustum?
 Proving the validity of an algorithm to solve $y' = f_1y+f_2$
 Characterization for the convergence in distribution
 Integration involving a fraction
 Line bundle on projective $A$scheme is the difference between two very ample line bundles
entityQuery vs. entityTypeManager
I have a custom content type user_in_club and I'd like to load a single specific node matching two field values. There are 2 ways (I know of) which can solve this:
$result = \Drupal::entityQuery('node')
>condition('type', 'user_in_club')
>condition('field_user_id', $account>id())
>condition('field_club_id',$active_club)
>execute();
$nodes = \Drupal::entityTypeManager()>getStorage('node')>loadMultiple($result);
OR
$nodes = \Drupal::entityTypeManager()
>getStorage('node')
>loadByProperties(['type' => 'user_in_club', 'field_user_id' => $account>id(), 'field_club_id' => $active_club ]);
In my single example only one node id is returned, but in case I have multiple node ids returned, is one method to be preferred over the other in terms of performance etc ? I currently don't see a big difference other than ETQ is better to create more complex queries.
They're identical. loadByProperties() actually converts your conditions to an entity query internally.

They're identical. loadByProperties() actually converts your conditions to an entity query internally.
I'd acually recommend to do an entity query yourself, directly. It's more readable and loadByProperties() might get deprecated in the future.
20170921 13:22:52