From 3a8d19a5253b775fe59038a9f0d9321a4ed4a6ae Mon Sep 17 00:00:00 2001 From: Thomas Lange Date: Sat, 29 Apr 2017 20:15:30 +0200 Subject: Markdown formatting for NULL added. --- Database.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Database.md b/Database.md index 762c67d..5e49fed 100644 --- a/Database.md +++ b/Database.md @@ -8,7 +8,7 @@ In this table are all created page objects stored and will be removed if the adm * Column `slug`: Contains the slug part of the pages absolute URL * Column `name`: Contains the name of the page * Column `body`: Contains the body of the page in the markdown format -* Column `argv`: Contains the optional argument string or is NULL +* Column `argv`: Contains the optional argument string or is `NULL` ## Table `post` [`MyISAM`] In this table are all created post objects stored and will be removed if the admin deletes them. @@ -21,7 +21,7 @@ The table type is `MyISAM` because the fulltext search doesn't work with `InnoDB * Column `slug`: Contains the slug part of the posts absolute URL * Column `name`: Contains the name of the post * Column `body`: Contains the body of the post in the markdown format -* Column `argv`: Contains the optional argument string or is NULL +* Column `argv`: Contains the optional argument string or is `NULL` ## Table `user` [`InnoDB`] In this table are all created user objects stored and will be removed if the admin deletes them. @@ -35,7 +35,7 @@ In this table are all created user objects stored and will be removed if the adm * Column `fullname`: Contains the full name of the user * Column `mailaddr`: Contains the contact email address of the user * Column `body`: Contains the body of the user in the markdown format -* Column `argv`: Contains the optional argument string or is NULL +* Column `argv`: Contains the optional argument string or is `NULL` ## Why database table prefixes are not supported The blogging application does not support the definition of a prefix for the database tables. This is because one database should only contain the data from one application (and if this is the case, prefixes are unnecessary). If multiple applications are sharing the same database and a security vulnerability is discovered in one of those applications, an attacker may be able to manipulate the data from the second application through the security vulnerability in the first application. \ No newline at end of file -- cgit v1.2.3