summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorThomas Lange <code@nerdmind.de>2017-04-29 20:11:07 +0200
committerThomas Lange <code@nerdmind.de>2017-04-29 20:11:07 +0200
commit36b8960f741d112f0ca60bf1c2779c782a527220 (patch)
tree0f5529fa34eb1f43bd2a8219bf95fa8cac24f29f
parentc8312fdacaa78a179061a671e7933fad42a4fd5b (diff)
downloadwiki-36b8960f741d112f0ca60bf1c2779c782a527220.tar.gz
wiki-36b8960f741d112f0ca60bf1c2779c782a527220.tar.xz
wiki-36b8960f741d112f0ca60bf1c2779c782a527220.zip
Note about prefixes edited.
-rw-r--r--Database.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/Database.md b/Database.md
index 544a487..b3bc131 100644
--- a/Database.md
+++ b/Database.md
@@ -35,4 +35,4 @@ In this table are all created user objects stored and will be removed if the adm
* Column `body`: Contains the body of the user in the markdown format
## 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 access the data from the second application through the security vulnerability in the first application. \ No newline at end of file
+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