Update most versions to include mysql 3.22.X warning

This commit is contained in:
Miles Lott 2001-08-13 17:51:23 +00:00
parent 4b909ae2bb
commit 38419e27f9
6 changed files with 1000 additions and 828 deletions

Binary file not shown.

View File

@ -1339,6 +1339,21 @@ This limits the maximum length for a tablename to 27 characters.
further limited to 21 characters in which to describe your table. further limited to 21 characters in which to describe your table.
You will need to be less descriptive in some cases, e.g. You will need to be less descriptive in some cases, e.g.
use 'phpgw_widget_cats' instead of 'phpgw_widget_info_categories'. use 'phpgw_widget_cats' instead of 'phpgw_widget_info_categories'.
\layout Standard
To maintain compatibility with MySQL 3.22.X, please always add
\begin_inset Quotes eld
\end_inset
'nullable' => False
\begin_inset Quotes erd
\end_inset
to your field spec for an auto field.
This and probably older versions of MySQL require that specification within
the SQL for a field that will also be an index or unique field, which for
our uses should typically be true for an auto field.
MySQL 3.23.X and PostgreSQL do not have this issue.
\layout Subsubsection \layout Subsubsection
Default 0 Default 0

Binary file not shown.

File diff suppressed because it is too large Load Diff

View File

@ -807,6 +807,9 @@
<para> <para>
This limits the maximum length for a tablename to 27 characters. Based on the tablename standard in phpgw of 'phpgw_tablename', you are further limited to 21 characters in which to describe your table. You will need to be less descriptive in some cases, e.g. use 'phpgw_widget_cats' instead of 'phpgw_widget_info_categories'. This limits the maximum length for a tablename to 27 characters. Based on the tablename standard in phpgw of 'phpgw_tablename', you are further limited to 21 characters in which to describe your table. You will need to be less descriptive in some cases, e.g. use 'phpgw_widget_cats' instead of 'phpgw_widget_info_categories'.
</para> </para>
<para>
To maintain compatibility with MySQL 3.22.X, please always add &ldquo;'nullable' =&gt; False&rdquo; to your field spec for an auto field. This and probably older versions of MySQL require that specification within the SQL for a field that will also be an index or unique field, which for our uses should typically be true for an auto field. MySQL 3.23.X and PostgreSQL do not have this issue.
</para>
</sect3> </sect3>
<sect3> <sect3>
<title> <title>

View File

@ -882,6 +882,14 @@ you are further limited to 21 characters in which to describe
your table. You will need to be less descriptive in some your table. You will need to be less descriptive in some
cases, e.g. use 'phpgw_widget_cats' instead of 'phpgw_widget_info_categories'. cases, e.g. use 'phpgw_widget_cats' instead of 'phpgw_widget_info_categories'.
To maintain compatibility with MySQL 3.22.X, please always
add "'nullable' => False" to
your field spec for an auto field. This and probably older
versions of MySQL require that specification within the
SQL for a field that will also be an index or unique field,
which for our uses should typically be true for an auto
field. MySQL 3.23.X and PostgreSQL do not have this issue.
5.1.2 Default 0 5.1.2 Default 0
For int fields, a default of 0 is not assumed. Only some For int fields, a default of 0 is not assumed. Only some