1. 08 May, 2007 1 commit
  2. 17 Apr, 2007 1 commit
  3. 13 Apr, 2007 1 commit
  4. 27 Mar, 2007 1 commit
  5. 11 Feb, 2007 1 commit
  6. 04 Feb, 2007 2 commits
  7. 02 Jan, 2007 1 commit
  8. 08 Dec, 2006 1 commit
  9. 05 Dec, 2006 1 commit
  10. 28 Nov, 2006 1 commit
  11. 24 Nov, 2006 1 commit
  12. 21 Nov, 2006 1 commit
  13. 16 Nov, 2006 1 commit
  14. 23 Oct, 2006 1 commit
  15. 12 Oct, 2006 1 commit
  16. 07 Sep, 2006 1 commit
  17. 05 Sep, 2006 1 commit
  18. 01 Sep, 2006 4 commits
  19. 23 Aug, 2006 1 commit
  20. 18 Aug, 2006 2 commits
  21. 08 Aug, 2006 1 commit
  22. 03 Aug, 2006 2 commits
  23. 31 Jul, 2006 1 commit
  24. 29 Jul, 2006 1 commit
  25. 19 Jul, 2006 1 commit
  26. 13 Jul, 2006 1 commit
  27. 11 Apr, 2006 1 commit
  28. 21 Jan, 2006 1 commit
  29. 09 Dec, 2005 2 commits
  30. 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