1. 04 Apr, 2006 3 commits
  2. 02 Apr, 2006 2 commits
  3. 31 Mar, 2006 1 commit
  4. 28 Mar, 2006 1 commit
  5. 23 Mar, 2006 1 commit
  6. 07 Mar, 2006 1 commit
  7. 04 Mar, 2006 1 commit
  8. 27 Feb, 2006 3 commits
  9. 26 Feb, 2006 2 commits
  10. 21 Feb, 2006 1 commit
  11. 12 Feb, 2006 1 commit
  12. 10 Feb, 2006 1 commit
  13. 09 Feb, 2006 1 commit
  14. 05 Feb, 2006 1 commit
  15. 01 Feb, 2006 2 commits
  16. 29 Jan, 2006 1 commit
  17. 24 Jan, 2006 2 commits
  18. 22 Jan, 2006 1 commit
  19. 21 Jan, 2006 1 commit
  20. 17 Jan, 2006 1 commit
  21. 12 Jan, 2006 1 commit
  22. 05 Jan, 2006 2 commits
  23. 04 Jan, 2006 1 commit
  24. 02 Jan, 2006 1 commit
  25. 31 Dec, 2005 1 commit
  26. 27 Dec, 2005 1 commit
  27. 22 Dec, 2005 1 commit
  28. 21 Dec, 2005 1 commit
  29. 16 Dec, 2005 1 commit
  30. 09 Dec, 2005 1 commit
  31. 08 Dec, 2005 1 commit
    • Dries's avatar
      - Patch #40341 by Neil: fixed problems with database schema versions. · c54234d7
      Dries authored
        - When user #1 creates an account (we can assume this happens only once), system.module's schema version is set to the latest availiable.
        - system_get_files_database() now includes a 'schema_version' child of each file object.
        - That new information is re-saved when Drupal re-populates the system table.
        - An array of newly-enabled modules is built, module_list() is reloaded, and the schema versions of each newly-enabled module are set to the most recent availiable. If the schema version is already set (presumably from a previous installation) it is not changed.
      c54234d7