Ticket #165 (new improve feature)
Splitting the database
| Reported by: | jeanyves | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | FrameWork | Keywords: | MYSQL,Database,BWport |
| Cc: |
Description
In the beginning with Old BW code, database where splited in three area :
- BW_MAIN which contain most of the tables
- BW_ARCHIVE which contain old logs produced by the LogStr?() function and previous version of text changed from the memberstrads table (this is useful in case of bug and for tracability)
- BW_CRYPTED for crypted data
The first idea was to be able to manage the backup independently (BW_Archive not so often, BW_MAIN daily). It was also to be able to split the database easely on several server when it will be needed. And, finally, for BW_CRYPTED it was to be able to created database sysadmin using PHPMYADMIN who have no read access to members crypted data (this because I want to have a bunch of argument to say for sure that BW make a lot of thing to protect members private data).
All have been unified (because it was necessary for progress) in Rox, but I think we should keep it in mind. Typically I think the forum tables shoudl be kept in a dedicated BW_FORUM table because one day they will b stored on a dedicated server.
Nota, this database split is transparent for test environment unless you setup different variables inside config.php
