Skip to content

Latest commit

 

History

History
573 lines (371 loc) · 18.2 KB

File metadata and controls

573 lines (371 loc) · 18.2 KB

Database Forge Class

The Database Forge Class contains methods that help you manage your database.

Important

In order to initialize the Forge class, your database driver must already be running, since the Forge class relies on it.

Load the Forge Class as follows:

.. literalinclude:: forge/001.php

You can also pass another database group name to the DB Forge loader, in case the database you want to manage isn't the default one:

.. literalinclude:: forge/002.php

In the above example, we're passing the name of a different database group to connect to as the first parameter.

Permits you to create the database specified in the first parameter. Returns true/false based on success or failure:

.. literalinclude:: forge/003.php

An optional second parameter set to true will add IF EXISTS statement or will check if a database exists before creating it (depending on DBMS).

.. literalinclude:: forge/004.php

Permits you to drop the database specified in the first parameter. Returns true/false based on success or failure:

.. literalinclude:: forge/005.php

CodeIgniter supports creating databases straight from your favorite terminal using the dedicated db:create command. By using this command it is assumed that the database is not yet existing. Otherwise, CodeIgniter will complain that the database creation has failed.

To start, just type the command and the name of the database (e.g., foo):

php spark db:create foo

If everything went fine, you should expect the Database "foo" successfully created. message displayed.

If you are on a testing environment or you are using the SQLite3 driver, you may pass in the file extension for the file where the database will be created using the --ext option. Valid values are db and sqlite and defaults to db. Remember that these should not be preceded by a period. :

php spark db:create foo --ext sqlite

The above command will create the db file in WRITEPATH/foo.sqlite.

Note

When using the special SQLite3 database name :memory:, expect that the command will still produce a success message but no database file is created. This is because SQLite3 will just use an in-memory database.

There are several things you may wish to do when creating tables. Add fields, add keys to the table, alter columns. CodeIgniter provides a mechanism for this.

$forge->addField()

Fields are normally created via an associative array. Within the array, you must include a type key that relates to the datatype of the field.

For example, INT, VARCHAR, TEXT, etc. Many datatypes (for example VARCHAR) also require a constraint key.

.. literalinclude:: forge/006.php

Additionally, the following key/values can be used:

  • unsigned/true : to generate UNSIGNED in the field definition.
  • default/value : to generate DEFAULT constraint in the field definition.
  • null/true : to generate NULL in the field definition. Without this, the field will default to NOT NULL.
  • auto_increment/true : generates an auto_increment flag on the field. Note that the field type must be a type that supports this, such as INTEGER.
  • unique/true : to generate a unique key for the field definition.
.. literalinclude:: forge/007.php

After the fields have been defined, they can be added using $forge->addField($fields) followed by a call to the :ref:`createTable() <creating-a-table>` method.

Notes on Data Types

Floating-Point Types

Floating-Point types such as FLOAT and DOUBLE represent approximate values. Therefore, they should not be used when exact values are needed.

mysql> CREATE TABLE t (f FLOAT, d DOUBLE);
mysql> INSERT INTO t VALUES(99.9, 99.9);

mysql> SELECT * FROM t WHERE f=99.9;
Empty set (0.00 sec)

mysql> SELECT * FROM t WHERE f > 99.89 AND f < 99.91;
+------+------+
| f    | d    |
+------+------+
| 99.9 | 99.9 |
+------+------+
1 row in set (0.01 sec)

When it is important to preserve exact precision, for example with monetary data, DECIMAL or NUMERIC should be used.

TEXT

TEXT should not be used on SQLSRV. It is deprecated. See ntext, text, and image (Transact-SQL) - SQL Server | Microsoft Learn.

ENUM

Not all databases support ENUM.

Starting with v4.5.0, SQLSRV Forge converts ENUM data types to VARCHAR(n). Previous versions converted to TEXT.

Raw Sql Strings as Default Values

.. versionadded:: 4.2.0

Since v4.2.0, $forge->addField() accepts a CodeIgniter\Database\RawSql instance, which expresses raw SQL strings.

.. literalinclude:: forge/027.php

Warning

When you use RawSql, you MUST escape the data manually. Failure to do so could result in SQL injections.

Passing Strings as Fields

If you know exactly how you want a field to be created, you can pass the string into the field definitions with addField():

.. literalinclude:: forge/008.php

Note

Passing raw strings as fields cannot be followed by addKey() calls on those fields.

Note

Multiple calls to addField() are cumulative.

Creating an id Field

There is a special exception for creating id fields. A field with type id will automatically be assigned as an INT(9) auto_incrementing Primary Key.

.. literalinclude:: forge/009.php

$forge->addKey()

Generally speaking, you'll want your table to have Keys. This is accomplished with $forge->addKey('field'). The optional second parameter set to true will make it a primary key and the third parameter set to true will make it a unique key. You may specify a name with the fourth parameter. Note that addKey() must be followed by a call to createTable() or processIndexes() when the table already exists.

Multiple column non-primary keys must be sent as an array. Sample output below is for MySQL.

.. literalinclude:: forge/010.php

$forge->addPrimaryKey()

$forge->addUniqueKey()

To make code reading more objective it is also possible to add primary and unique keys with specific methods:

.. literalinclude:: forge/011.php

Note

When you add a primary key, MySQL and SQLite will assume the name PRIMARY even if a name is provided.

Foreign Keys help to enforce relationships and actions across your tables. For tables that support Foreign Keys, you may add them directly in forge:

.. literalinclude:: forge/012.php

You can specify the desired action for the "on update" and "on delete" properties of the constraint as well as the name:

.. literalinclude:: forge/013.php

Note

SQLite3 does not support the naming of foreign keys. CodeIgniter will refer to them by prefix_table_column_foreign.

After fields and keys have been declared, you can create a new table with

.. literalinclude:: forge/014.php

An optional second parameter set to true will create the table only if it doesn't already exist.

.. literalinclude:: forge/015.php

You could also pass optional table attributes, such as MySQL's ENGINE:

.. literalinclude:: forge/016.php

Note

Unless you specify the CHARACTER SET and/or COLLATE attributes, createTable() will always add them with your configured charset and DBCollat values, as long as they are not empty (MySQL only).

Execute a DROP TABLE statement and optionally add an IF EXISTS clause.

.. literalinclude:: forge/017.php

A third parameter can be passed to add a CASCADE option, which might be required for some drivers to handle removal of tables with foreign keys.

.. literalinclude:: forge/018.php

$forge->addColumn()

The addColumn() method is used to modify an existing table. It accepts the same field array as :ref:`Creating Tables <adding-fields>`, and can be used to add additional fields.

Note

Unlike when creating a table, if null is not specified, the column will be NULL, not NOT NULL.

.. literalinclude:: forge/022.php

If you are using MySQL or CUBIRD, then you can take advantage of their AFTER and FIRST clauses to position the new column.

Examples:

.. literalinclude:: forge/023.php

$forge->dropColumn()

Used to remove a column from a table.

.. literalinclude:: forge/024.php

Used to remove multiple columns from a table.

.. literalinclude:: forge/025.php

$forge->modifyColumn()

The usage of this method is identical to addColumn(), except it alters an existing column rather than adding a new one. In order to change the name, you can add a "name" key into the field defining array.

.. literalinclude:: forge/026.php

Note

The modifyColumn() may unexpectedly change NULL/NOT NULL. So it is recommended to always specify the value for null key. Unlike when creating a table, if null is not specified, the column will be NULL, not NOT NULL.

Note

Due to a bug, prior v4.3.4, SQLite3 may not set NOT NULL even if you specify 'null' => false.

Note

Due to a bug, prior v4.3.4, Postgres and SQLSRV set NOT NULL even if you specify 'null' => true.

.. versionadded:: 4.3.0

You may add keys to an existing table by using addKey(), addPrimaryKey(), addUniqueKey() or addForeignKey() and processIndexes():

.. literalinclude:: forge/029.php

.. versionadded:: 4.3.0

Execute a DROP PRIMARY KEY.

.. literalinclude:: forge/028.php

Execute a DROP KEY.

.. literalinclude:: forge/020.php

Execute a DROP FOREIGN KEY.

.. literalinclude:: forge/019.php

Executes a TABLE rename

.. literalinclude:: forge/021.php

.. php:namespace:: CodeIgniter\Database

.. php:class:: Forge

    .. php:method:: addColumn($table[, $field = []])

        :param    string    $table: Table name to add the column to
        :param    array    $field: Column definition(s)
        :returns:    true on success, false on failure
        :rtype:    bool

        Adds a column to an existing table. Usage: See `Adding a Field to a Table`_.

    .. php:method:: addField($field)

        :param    array    $field: Field definition to add
        :returns:    ``\CodeIgniter\Database\Forge`` instance (method chaining)
        :rtype:    ``\CodeIgniter\Database\Forge``

        Adds a field to the set that will be used to create a table. Usage: See `Adding Fields`_.

    .. php:method:: addForeignKey($fieldName, $tableName, $tableField[, $onUpdate = '', $onDelete = '', $fkName = ''])

        :param    string|string[]    $fieldName: Name of a key field or an array of fields
        :param    string    $tableName: Name of a parent table
        :param    string|string[]    $tableField: Name of a parent table field or an array of fields
        :param    string    $onUpdate: Desired action for the "on update"
        :param    string    $onDelete: Desired action for the "on delete"
        :param    string    $fkName: Name of foreign key. This does not work with SQLite3
        :returns:    ``\CodeIgniter\Database\Forge`` instance (method chaining)
        :rtype:    ``\CodeIgniter\Database\Forge``

        Adds a foreign key to the set that will be used to create a table. Usage: See `Adding Foreign Keys`_.

        .. note:: ``$fkName`` can be used since v4.3.0.

    .. php:method:: addKey($key[, $primary = false[, $unique = false[, $keyName = '']]])

        :param    mixed    $key: Name of a key field or an array of fields
        :param    bool    $primary: Set to true if it should be a primary key or a regular one
        :param    bool    $unique: Set to true if it should be a unique key or a regular one
        :param    string    $keyName: Name of key to be added
        :returns:    ``\CodeIgniter\Database\Forge`` instance (method chaining)
        :rtype:    ``\CodeIgniter\Database\Forge``

        Adds a key to the set that will be used to create a table. Usage: See `Adding Keys`_.

        .. note:: ``$keyName`` can be used since v4.3.0.

    .. php:method:: addPrimaryKey($key[, $keyName = ''])

        :param    mixed    $key: Name of a key field or an array of fields
        :param    string    $keyName: Name of key to be added
        :returns:    ``\CodeIgniter\Database\Forge`` instance (method chaining)
        :rtype:    ``\CodeIgniter\Database\Forge``

        Adds a primary key to the set that will be used to create a table. Usage: See `Adding Keys`_.

        .. note:: ``$keyName`` can be used since v4.3.0.

    .. php:method:: addUniqueKey($key[, $keyName = ''])

        :param    mixed    $key: Name of a key field or an array of fields
        :param    string    $keyName: Name of key to be added
        :returns:    ``\CodeIgniter\Database\Forge`` instance (method chaining)
        :rtype:    ``\CodeIgniter\Database\Forge``

        Adds a unique key to the set that will be used to create a table. Usage: See `Adding Keys`_.

        .. note:: ``$keyName`` can be used since v4.3.0.

    .. php:method:: createDatabase($dbName[, $ifNotExists = false])

        :param    string    $db_name: Name of the database to create
        :param    string    $ifNotExists: Set to true to add an ``IF NOT EXISTS`` clause or check if database exists
        :returns:    true on success, false on failure
        :rtype:    bool

        Creates a new database. Usage: See `Creating and Dropping Databases`_.

    .. php:method:: createTable($table[, $if_not_exists = false[, array $attributes = []]])

        :param    string    $table: Name of the table to create
        :param    string    $if_not_exists: Set to true to add an ``IF NOT EXISTS`` clause
        :param    string    $attributes: An associative array of table attributes
        :returns:  Query object on success, false on failure
        :rtype:    mixed

        Creates a new table. Usage: See `Creating a Table`_.

    .. php:method:: dropColumn($table, $columnNames)

        :param    string    $table: Table name
        :param    mixed    $columnNames: Comma-delimited string or an array of column names
        :returns:    true on success, false on failure
        :rtype:    bool

        Drops single or multiple columns from a table. Usage: See `Dropping Fields From a Table`_.

    .. php:method:: dropDatabase($dbName)

        :param    string    $dbName: Name of the database to drop
        :returns:    true on success, false on failure
        :rtype:    bool

        Drops a database. Usage: See `Creating and Dropping Databases`_.

    .. php:method:: dropKey($table, $keyName[, $prefixKeyName = true])

        :param    string    $table: Name of table that has key
        :param    string    $keyName: Name of key to be dropped
        :param    string    $prefixKeyName: If database prefix should be added to ``$keyName``
        :returns:    true on success, false on failure
        :rtype:    bool

        Drops an index or unique index.

        .. note:: ``$keyName`` and ``$prefixKeyName`` can be used since v4.3.0.

    .. php:method:: dropPrimaryKey($table[, $keyName = ''])

        :param    string    $table: Name of table to drop primary key
        :param    string    $keyName: Name of primary key to be dropped
        :returns:    true on success, false on failure
        :rtype:    bool

        Drops a primary key from a table.

        .. note:: ``$keyName`` can be used since v4.3.0.

    .. php:method:: dropTable($table_name[, $if_exists = false])

        :param    string    $table: Name of the table to drop
        :param    string    $if_exists: Set to true to add an ``IF EXISTS`` clause
        :returns:    true on success, false on failure
        :rtype:    bool

        Drops a table. Usage: See `Dropping a Table`_.

    .. php:method:: processIndexes($table)

        .. versionadded:: 4.3.0

        :param    string    $table: Name of the table to add indexes to
        :returns:    true on success, false on failure
        :rtype:    bool

        Used following ``addKey()``, ``addPrimaryKey()``, ``addUniqueKey()``,
        and ``addForeignKey()`` to add indexes to an existing table.
        See `Adding Keys to a Table`_.

    .. php:method:: modifyColumn($table, $field)

        :param    string    $table: Table name
        :param    array    $field: Column definition(s)
        :returns:    true on success, false on failure
        :rtype:    bool

        Modifies a table column. Usage: See `Modifying a Field in a Table`_.

    .. php:method:: renameTable($tableName, $newTableName)

        :param    string    $tableName: Current of the table
        :param    string    $newTableName: New name of the table
        :returns:  Query object on success, false on failure
        :rtype:    mixed

        Renames a table. Usage: See `Renaming a Table`_.