Manual:Coding conventions/Database

used within files of the written for usage with a Database. See also the that apply to all program languages, including those for database If you would like a short checklist to help you review your commits, try using th.

== Use UPPERCASE for MySQL/MariaDB keywords, and lowercase for things like types Do not specify the lengths of numeric types, but do fo an type for all timestamps, and parse them to the standard format using ; do not use the field type Make sure to include t comment immediately before any table name; this will be replaced with the wiki's if necessary, and omittingis clearer and makes it easier to see the difference between unique and non-unique indices  Don't create indices wi == the same SQL as MySQL/MariaDB, so the SQL must be compatible with bot Usually, this can be accomplished with a few simple rules, given afrom the table name: the name itself if it's short, or an When updating the schema for an extension, it is advisable to both update the original schema file and create a patch file for those urevious version.