* one from the pool. We must take the pooled connection because by taking it from the pool, we've
   * fully acquired it.
   *
   * This test yields threads to force the decision of plan1 to be deliberate and not lucky. In
   * particular, we set up this sequence of events:
   *
   *  1. take plan 0
   *  3. plan 0 connects
   *  4. finish taking plan 1
   *

  /**
   * Divides an iterable into unmodifiable sublists of the given size (the final iterable may be
   * smaller). For example, partitioning an iterable containing {@code [a, b, c, d, e]} with a
   * partition size of 3 yields {@code [[a, b, c], [d, e]]} -- an outer iterable containing two
   * inner lists of three and two elements, all in the original order.
   *

     * the encoded path will have a trailing '/'.
     *
     * Popping "/a/b/c/" yields "/a/b/". In this case the list of path segments goes from ["a",
     * "b", "c", ""] to ["a", "b", ""].
     *
     * Popping "/a/b/c" also yields "/a/b/". The list of path segments goes from ["a", "b", "c"]
     * to ["a", "b", ""].
     */
    private fun pop() {

   * usually have much noticeable impact. A value of one permits only one thread to modify the cache
   * at a time, but since read operations and cache loading computations can proceed concurrently,
   * this still yields higher concurrency than full synchronization.
   *
   * <p>Defaults to 4. <b>Note:</b>The default may change in the future. If you care about this
   * value, you should always choose it explicitly.
   *

   * size (the final list may be smaller). For example, partitioning a list containing {@code [a, b,
   * c, d, e]} with a partition size of 3 yields {@code [[a, b, c], [d, e]]} -- an outer list
   * containing two inner lists of three and two elements, all in the original order.
   *

    }

    public void test_setResponseFields() {
        String[] fields = { "field1", "field2", "field3" };
        queryFieldConfig.setResponseFields(fields);

        assertSame(fields, queryFieldConfig.responseFields);
    }

    public void test_getScrollResponseFields() {
        String[] fields = { "scroll1", "scroll2", "scroll3" };
        queryFieldConfig.setScrollResponseFields(fields);

사실, FastAPI는 내부적으로 이 두 데코레이터를 사용합니다.

///

## `yield`를 사용하는 데이터베이스 의존성

예를 들어, 이 기능을 사용하면 데이터베이스 세션을 생성하고 작업이 끝난 후에 세션을 종료할 수 있습니다.

응답을 생성하기 전에는 `yield`문을 포함하여 그 이전의 코드만이 실행됩니다:

{* ../../docs_src/dependencies/tutorial007.py hl[2:4] *}

yield된 값은 *경로 작업* 및 다른 의존성들에 주입되는 값 입니다:

{* ../../docs_src/dependencies/tutorial007.py hl[4] *}

`yield`문 다음의 코드는 응답을 생성한 후 보내기 전에 실행됩니다:

# Body - Fields { #body-fields }

The same way you can declare additional validation and metadata in *path operation function* parameters with `Query`, `Path` and `Body`, you can declare validation and metadata inside of Pydantic models using Pydantic's `Field`.

## Import `Field` { #import-field }

First, you have to import it:

{* ../../docs_src/body_fields/tutorial001_an_py310.py hl[4] *}


/// warning

        facetInfo.size = 20;
        facetInfo.sort = "term.asc";

        String result = facetInfo.toString();
        assertEquals("FacetInfo [field=[field1], query=null, size=20, minDocCount=null, sort=term.asc, missing=null]", result);
    }

    // Test field assignment
    public void test_fieldAssignment() {
        String[] fields = new String[] { "field1", "field2", "field3" };

        String[] roles = { "role2", "role1" };
        String[] fields = { "field2", "field1" };
        String[] excludes = { "exclude2", "exclude1" };

        String result1 = popularWordHelper.getCacheKey(seed, tags, roles, fields, excludes);
        String result2 = popularWordHelper.getCacheKey(seed, tags, roles, fields, excludes);

        assertEquals(result1, result2);
    }