documentation.txt 1.0 KB

1234567891011121314151617181920212223
  1. There are SQL sequences that should not neccessarily be performed every time you
  2. update your database structure. Rather, these queries should be executed once or
  3. from time to time. Essentially, an .sql file should appear under 'maintenance'
  4. instead of the old 'updates' folder provided that:
  5. - Its execution isn't mandatory to keep L2J setups working past any core revision
  6. number. (e.g. orphans cleanup)
  7. - Its execution were time consuming and could slowdown regular database update tasks.
  8. (e.g. complex sub/queries, joins)
  9. - Its execution could allow administrators to perform optimization, maintenance,
  10. repair or recovery tasks whenever they needed to.
  11. Any SQL maintenance should be named like that:
  12. YYYYMMDDmaintenance(_s).sql
  13. See the updates directory documentation for further details of the naming convention.
  14. Additionally, it would be desirable that any maintenance script could hold internal
  15. documentation describing their specific purpose, execution scenario and any other
  16. information that could be of interest for the administrator.