map:{
    # /- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    # o database: (Required)
    #  This is the target database, only considered when generating
    #  the SQL for your DBFlute project.
    #  Your possible choices are:
    #
    #    mysql, postgresql, oracle, db2, sqlserver,
    #    h2, derby, (sqlite, firebird, msaccess)
    #
    ; database = h2
    # - - - - - - - - - -/

And the spec says that the fields have to be named like that. So `user-name` or `email` wouldn't work.

But don't worry, you can show it as you wish to your final users in the frontend.

And your database models can use any other names you want.

But for the login *path operation*, we need to use these names to be compatible with the spec (and be able to, for example, use the integrated API documentation system).

    #   [true]
    #     Generate the method that depends on the database. e.g. cb.lockWithRR() at DB2.
    #
    #; isAvailableDatabaseDependency = false
    # - - - - - - - - - -/

    # /- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    # o isAvailableDatabaseNativeJDBC: (NotRequired - Default false)
    #   [true]
    #     Use classes of database native JDBC on generated classes to get best performances of DB access.

So, you would be able to, for example, share the same data from a Django application in a database with a FastAPI application. Or gradually migrate a Django application using the same database.

And your users would be able to login from your Django app or from your **FastAPI** app, at the same time.

///

        super();
    }

    /**
     * Behavior class for file configuration database operations.
     * Provides access to the file configuration entity operations.
     */
    @Resource
    protected FileConfigBhv fileConfigBhv;

    /**
     * Behavior class for file authentication database operations.
     * Manages authentication configurations associated with file configurations.
     */

package gorm

import (
	"context"
	"database/sql"

	"gorm.io/gorm/clause"
	"gorm.io/gorm/schema"
)

// Dialector GORM database dialector
type Dialector interface {
	Name() string
	Initialize(*DB) error
	Migrator(db *DB) Migrator
	DataTypeOf(*schema.Field) string
	DefaultValueOf(*schema.Field) clause.Expression
	BindVarTo(writer clause.Writer, stmt *Statement, v interface{})
	QuoteTo(clause.Writer, string)

import org.apache.maven.api.annotations.Nonnull;
import org.apache.maven.api.annotations.Nullable;

/**
 * Provides access to the contents of a source independently of the
 * backing store (e.g. file system, database, memory).
 * <p>
 * This is mainly used to parse files into objects such as Maven projects,
 * models, settings, or toolchains. The source implementation handles

	type City struct {
		gorm.Model
		Name string `gorm:"unique"`
	}

	db, err := OpenTestConnection(&gorm.Config{TranslateError: true})
	if err != nil {
		t.Fatalf("failed to connect database, got error %v", err)
	}

	dialectors := map[string]bool{"sqlite": true, "postgres": true, "gaussdb": true, "mysql": true, "sqlserver": true}
	if supported, found := dialectors[db.Dialector.Name()]; !(found && supported) {

    }

    @Test
    public void testBufferCreation() throws UnsupportedEncodingException {
        byte[] dataBytes = { 1, 2, 3, 4 };
        String params = "test";
        byte[] buffer = createBuffer(10, dataBytes, params);

        // Verify buffer structure
        assertTrue(buffer.length >= 14, "Buffer should contain header, params and data");
    }

    @Test

            then
              echo "Creating database gorm..."
              sql_file='/tmp/create_database.sql'
              echo "CREATE DATABASE gorm DBCOMPATIBILITY 'PG';" > ${sql_file}
              docker cp "${sql_file}" "${container_name}":"${sql_file}"
              docker exec -i ${TTY_FLAG} "${container_name}" bash -c "su - omm -c 'gsql -U omm -f ${sql_file}'"
              echo "Database initialization completed."
              break