{* ../../docs_src/sql_databases/tutorial001_an_py310.py ln[25:30] hl[25:27,30] *}

### Criar Tabelas de Banco de Dados na Inicialização

Vamos criar as tabelas do banco de dados quando o aplicativo for iniciado.

{* ../../docs_src/sql_databases/tutorial001_an_py310.py ln[32:37] hl[35:37] *}

Aqui, criamos as tabelas em um evento de inicialização do aplicativo.

 *
 * <p>See the Guava User Guide article on <a href=
 * "https://github.com/google/guava/wiki/CollectionUtilitiesExplained#tables">{@code Tables}</a>.
 *
 * @author Jared Levy
 * @author Louis Wasserman
 * @since 7.0
 */
@GwtCompatible
@ElementTypesAreNonnullByDefault
public final class Tables {
  private Tables() {}

  /**
   * Returns a {@link Collector} that accumulates elements into a {@code Table} created using the

{
  "labels": {
    "critical": {
      "name": "type:critical",
      "colour": "#E84137",
      "description": "critical questions"
    },
    "question": {
      "name": "type:question",
      "colour": "#EDEDED",
      "description": "general questions"
    },
    "feature": {
      "name": "type:feature_request",
      "colour": "#43952A",
      "description": "feature request"
    },
    "invalid_question": {

   *
   * <p>For empty or single-cell immutable tables, {@link #of()} and {@link #of(Object, Object,
   * Object)} are even more convenient.
   *
   * <p>Builder instances can be reused - it is safe to call {@link #buildOrThrow} multiple times to
   * build multiple tables in series. Each table is a superset of the tables created before it.
   *
   * @since 11.0
   */
  @DoNotMock

        if: contains(github.event.pull_request.labels.*.name, 'build and push to gcr.io for staging')
        uses: docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567 # v3.3.0
        with:
          registry: gcr.io
          username: _json_key
          password: ${{ secrets.GCP_CREDS }}
      -
        name: Login to AR
        # Once this is verified, change the label's name. For now, we will piggyback on gcr.io actions.

labels.purgeByBots	=	Purge par les bots
labels.logLevel	=	Niveau de journalisation
labels.purgeSearchLogDay	=	Purger le journal de recherche
labels.query	=	Requête
labels.queryId	=	ID de requête
labels.rt	=	rt
labels.searchLog	=	Journal de recherche
labels.sort	=	Trier
labels.start	=	Point de départ
labels.loginRequired	=	Connexion requise
labels.loginLink	=	Lien de connexion
labels.threadName	=	Nom du fil
labels.url	=	URL

```
/minio/metrics/v3/api/bucket?list
```

## Metric Categories

At a high level, metrics are grouped into categories as described in the following sections. The path in each of the tables is relative to the top-level endpoint. Note that the standard GoCollector metrics are not shown.

### Request metrics

Metrics about requests served by the current node.

labels.userInfo=User Info
labels.webApiJson=JSON Response
labels.webConfigName=Web Config Name
labels.allLanguages=All Languages
labels.dictId=Dictionary ID
labels.docId=Document ID
labels.endTime=End Time
labels.hq=hq
labels.inputs=Source
labels.jobLogging=Logging
labels.jobName=Name
labels.jobStatus=Status
labels.labelTypeIds=Labels
labels.lang=lang
labels.outputs=Target
labels.pos=POS

labels.userInfo=User Info
labels.webApiJson=JSON Response
labels.webConfigName=Web Config Name
labels.allLanguages=All Languages
labels.dictId=Dictionary ID
labels.docId=Document ID
labels.endTime=End Time
labels.hq=hq
labels.inputs=Source
labels.jobLogging=Logging
labels.jobName=Name
labels.jobStatus=Status
labels.labelTypeIds=Labels
labels.lang=lang
labels.outputs=Target
labels.pos=POS

<h3 id="searchOptionsLabel">
	<la:message key="labels.search_options" />
</h3>
<div>
	<fieldset class="form-group">
		<legend><la:message key="labels.index_num" /></legend>
		<label for="contentNum"><la:message key="labels.index_num" /></label>
		<la:select property="num" styleId="numSearchOption"
			styleClass="form-control">
			<option value="10">
				<la:message key="labels.search_result_select_num" />
			</option>