manual.texi Add SET_FLAG to manual. It's deprecated, but there's

manual.texi	an alternative non-deprecated way to test for SET.
parent c39faf15
...@@ -41010,15 +41010,16 @@ or more of the following bits set: ...@@ -41010,15 +41010,16 @@ or more of the following bits set:
@item @code{AUTO_INCREMENT_FLAG} @tab Field has the @code{AUTO_INCREMENT} @item @code{AUTO_INCREMENT_FLAG} @tab Field has the @code{AUTO_INCREMENT}
attribute attribute
@item @code{ENUM_FLAG} @tab Field is an @code{ENUM} (deprecated) @item @code{ENUM_FLAG} @tab Field is an @code{ENUM} (deprecated)
@item @code{SET_FLAG} @tab Field is a @code{SET} (deprecated)
@item @code{BLOB_FLAG} @tab Field is a @code{BLOB} or @code{TEXT} (deprecated) @item @code{BLOB_FLAG} @tab Field is a @code{BLOB} or @code{TEXT} (deprecated)
@item @code{TIMESTAMP_FLAG} @tab Field is a @code{TIMESTAMP} (deprecated) @item @code{TIMESTAMP_FLAG} @tab Field is a @code{TIMESTAMP} (deprecated)
@end multitable @end multitable
Use of the @code{BLOB_FLAG}, @code{ENUM_FLAG}, and @code{TIMESTAMP_FLAG} Use of the @code{BLOB_FLAG}, @code{ENUM_FLAG}, @code{SET_FLAG}, and
flags is deprecated because they indicate the type of a field rather @code{TIMESTAMP_FLAG} flags is deprecated because they indicate the type of
than an attribute of its type. It is preferable to test a field rather than an attribute of its type. It is preferable to test
@code{field->type} against @code{FIELD_TYPE_BLOB}, @code{field->type} against @code{FIELD_TYPE_BLOB}, @code{FIELD_TYPE_ENUM},
@code{FIELD_TYPE_ENUM}, or @code{FIELD_TYPE_TIMESTAMP} instead. @code{FIELD_TYPE_SET}, or @code{FIELD_TYPE_TIMESTAMP} instead.
@noindent @noindent
The example below illustrates a typical use of the @code{flags} value: The example below illustrates a typical use of the @code{flags} value:
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment