Update xmldb.md

[lucaboesch]

Ordering of the Conventions List as in https://docs.moodle.org/dev/XMLDB_defining_an_XML_structure. Note that the Github Markdown preview does not do accurately preview ordered lists second level numbers like they should appear see https://youtu.be/iBA-j6XaHNc?si=w1mE3--keCxcnxZR&t=333 I hope docusaurus then gets it right.

[netlify]

✅ Deploy Preview for moodledevdocs ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	4933162
🔍 Latest deploy log	https://app.netlify.com/sites/moodledevdocs/deploys/64ea25df1519ac0008bb6773
😎 Deploy Preview	https://deploy-preview-710--moodledevdocs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions]

⚡️ Lighthouse report for the deploy preview of this PR

URL	Performance	Accessibility	Best Practices	SEO	PWA	Report
/	🟠 74	🟠 87	🟢 92	🟢 90	🟢 100	Report
/docs/apis/commonfiles	🔴 38	🟠 85	🟢 92	🟢 100	🟢 100	Report
/general/development/gettingstarted	🟠 52	🟠 87	🟢 92	🟢 90	🟢 100	Report
/general/releases	🔴 47	🟠 87	🟢 92	🟢 100	🟢 100	Report

[andrewnicols]

Hi Luca,

How about simply indenting them?

1. About names:
    1. All lowercase names (tables, indexes, keys and fields).
    1. Table names and field names must use only a-z, 0-9 and _ chars. Max 28 characters.
    1. Key and index names under the XMLDB Files must be formed by concatenating the name of the fields present in the key/index with the '"-" (minus) character.
    1. Primary key always must be named "primary" (this is one exception to the previous convention).
    1. It's highly recommended to avoid [reserved words](https://docs.moodle.org/dev/XMLDB_reserved_words) completely. We know we have some of them now but they should be completely out for next releases.
1. About NULLS
    1. Avoid to create all the fields as NOT NULL with the *silly* default value `*` (empty string). The underlying code used to create tables will handle it properly but the XMLDB structure must be REAL. Read more in the [Problems Page](https://docs.moodle.org/dev/XMLDB_Problems#NOT_NULL_fields_using_a_DEFAULT_*_clause).
1. About FOREIGN KEYS
    1. Under the tables of every XMLDB file, you must define the existing **Foreign Keys** (FK) properly. This will allow everybody to know a bit better the structure, allow to evolve to a better constrained system in the future and will provide the underlying code with the needed info to create the proper indexes.
    1. Note that, if you define any field combination as FK you won't have to create any index on that fields, the code will do it automatically!
    1. Respect Convention 1.3
1. About UNIQUE KEYS
    1. Declare any fields as UNIQUE KEY (UK) only if they are going to be used as target for one FK. Create unique indexes instead.
    1. Respect Convention 1.3

No need for all of this HTML.

[lucaboesch]

Okay fair enough @andrewnicols
I tried do do this in Markdown and submitted another, amended, commit.

[lucaboesch]

Yet, as I was fearing, it does not take arabic (1,2,3) numbers for the sublists.

I think there's no way around this except some coding in HTML.

That has to be arabic because it is consistently referring to point 1.3…