diff options
| author | Thomas Lange <code@nerdmind.de> | 2017-04-29 20:07:56 +0200 |
|---|---|---|
| committer | Thomas Lange <code@nerdmind.de> | 2017-04-29 20:07:56 +0200 |
| commit | c8312fdacaa78a179061a671e7933fad42a4fd5b (patch) | |
| tree | 90f808408e3574c58262a9c5d2a26a8878511401 | |
| parent | 6b7dd2408a7984154612c215cd72b2b297f0d2ce (diff) | |
| download | wiki-c8312fdacaa78a179061a671e7933fad42a4fd5b.tar.gz wiki-c8312fdacaa78a179061a671e7933fad42a4fd5b.tar.xz wiki-c8312fdacaa78a179061a671e7933fad42a4fd5b.zip | |
Not about prefixes added.
| -rw-r--r-- | Database.md | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/Database.md b/Database.md index afd0968..544a487 100644 --- a/Database.md +++ b/Database.md @@ -32,4 +32,7 @@ In this table are all created user objects stored and will be removed if the adm * Column `password`: Contains the `bcrypt` hashed password of the user * 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
\ No newline at end of file +* 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 |