<div class="termy">

```console
$ pip install "fastapi[standard]"

---> 100%
```

</div>

**Note**: Make sure you put `"fastapi[standard]"` in quotes to ensure it works in all terminals.

## Example { #example }

### Create it { #create-it }

Nesse caso, seria melhor ter apenas 2 servidores e usar uma porcentagem maior de seus recursos (CPU, memória, disco, largura de banda de rede, etc).

Si vous venez d'un autre framework asynchrone qui ne fonctionne pas comme de la façon décrite ci-dessus et que vous êtes habitués à définir des *fonctions de chemin* basiques avec un simple `def` pour un faible gain de performance (environ 100 nanosecondes), veuillez noter que dans **FastAPI**, l'effet serait plutôt contraire. Dans ces cas-là, il vaut mieux utiliser `async def` à moins que votre *fonction de chemin* utilise du code qui effectue des opérations <abbr title="Input/Output ou...

      return result;
    }
    return new UnmodifiableIterable<>(iterable);
  }

  /**
   * Simply returns its argument.
   *
   * @deprecated no need to use this
   * @since 10.0
   */
  @InlineMe(
      replacement = "checkNotNull(iterable)",
      staticImports = "com.google.common.base.Preconditions.checkNotNull")
  @Deprecated

Si vienes de otro framework async que no funciona de la manera descrita anteriormente y estás acostumbrado a definir funciones de *path operation* solo de cómputo trivial con `def` normal para una pequeña ganancia de rendimiento (alrededor de 100 nanosegundos), ten en cuenta que en **FastAPI** el efecto sería bastante opuesto. En estos casos, es mejor usar `async def` a menos que tus *path operation functions* usen código que realice <abbr title="Input/Output: lectura o escritura en disco, comunicaciones...

        .containsExactly(
            list(0, 0, 0),
            list(0, 0, 1),
            list(0, 1, 0),
            list(0, 1, 1),
            list(1, 0, 0),
            list(1, 0, 1),
            list(1, 1, 0),
            list(1, 1, 1))
        .inOrder();
  }

  public void testCartesianProduct_contains() {

    assertTrue(len4.matches('d'));
    for (char c = 'e'; c < 'z'; c++) {
      assertFalse(len4.matches(c));
    }

    Random rand = new Random(1234);
    for (int testCase = 0; testCase < 100; testCase++) {
      char[] chars = randomChars(rand, rand.nextInt(63) + 1);
      CharMatcher m = SmallCharMatcher.from(bitSet(chars), new String(chars));
      checkExactMatches(m, chars);
    }
  }

        si++;
        sub_authority_count = src[si++];
        identifier_authority = new byte[6];
        System.arraycopy(src, si, identifier_authority, 0, 6);
        si += 6;
        if (sub_authority_count > 100) {
            throw new RuntimeException("Invalid SID sub_authority_count");
        }
        sub_authority = new int[sub_authority_count];
        for (int i = 0; i < sub_authority_count; i++) {

## `SQLModel` 설치하기

먼저, [가상 환경](../virtual-environments.md){.internal-link target=_blank}을 생성하고 활성화한 다음, `sqlmodel`을 설치하세요:

<div class="termy">

```console
$ pip install sqlmodel
---> 100%
```

</div>

## 단일 모델로 애플리케이션 생성하기

우선 단일 **SQLModel** 모델을 사용하여 애플리케이션의 가장 간단한 첫 번째 버전을 생성해보겠습니다.

이후 **다중 모델**을 추가하여 보안과 유연성을 강화할 것입니다. 🤓

### 모델 생성하기

`SQLModel`을 가져오고 데이터베이스 모델을 생성합니다:

pkg debug/elf, const R_ARM_ABS8 = 8
pkg debug/elf, const R_ARM_AMP_VCALL9 = 12
pkg debug/elf, const R_ARM_COPY = 20
pkg debug/elf, const R_ARM_GLOB_DAT = 21
pkg debug/elf, const R_ARM_GNU_VTENTRY = 100
pkg debug/elf, const R_ARM_GNU_VTINHERIT = 101
pkg debug/elf, const R_ARM_GOT32 = 26
pkg debug/elf, const R_ARM_GOTOFF = 24
pkg debug/elf, const R_ARM_GOTPC = 25
pkg debug/elf, const R_ARM_JUMP_SLOT = 22