Opened 11 years ago

Closed 6 years ago

#165 closed improve feature (wontfix)

Splitting the database

Reported by: jeanyves Owned by:
Priority: major Milestone: unassigned
Component: FrameWork Keywords: MYSQL, Database, BWport


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

Change History (4)

comment:1 Changed 11 years ago by philipp

  • Component changed from BV Forum to FrameWork
  • Keywords BWport added

comment:2 Changed 7 years ago by TimLoal

  • Milestone set to Future

comment:3 Changed 7 years ago by jsfan

  • Milestone Future deleted

Milestone Future deleted

comment:4 Changed 6 years ago by planetcruiser

  • Milestone set to unassigned
  • Resolution set to wontfix
  • Status changed from new to closed


Note: See TracTickets for help on using tickets.