Skip to content

docs: fix incorrect descriptions in Forge::modifyColumn() notes #8441

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 25, 2024
+3 −3
Merged

docs: fix incorrect descriptions in Forge::modifyColumn() notes #8441

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions user_guide_src/source/dbmgmt/forge.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -306,11 +306,11 @@ change the name, you can add a "name" key into the field defining array.
a table, if ``null`` is not specified, the column will be ``NULL``, not
``NOT NULL``.

.. note:: Due to a bug, prior v4.3.3, SQLite3 may not set ``NOT NULL`` even if you
.. 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.3, Postgres and SQLSRV 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``.

.. _db-forge-adding-keys-to-a-table:

Expand Down