1. 05 May, 2021 1 commit
  2. 18 Mar, 2021 2 commits
  3. 16 Mar, 2021 1 commit
  4. 15 Mar, 2021 1 commit
  5. 15 Dec, 2020 1 commit
  6. 17 Nov, 2020 1 commit
  7. 29 Sep, 2020 1 commit
  8. 08 Sep, 2020 1 commit
  9. 28 Jul, 2020 1 commit
  10. 09 Jun, 2020 1 commit
  11. 19 May, 2020 1 commit
  12. 12 May, 2020 1 commit
  13. 28 Apr, 2020 1 commit
  14. 31 Mar, 2020 1 commit
  15. 17 Feb, 2020 1 commit
  16. 17 Dec, 2019 2 commits
  17. 08 Nov, 2019 1 commit
  18. 30 Oct, 2019 1 commit
  19. 15 Oct, 2019 1 commit
  20. 20 Aug, 2019 1 commit
  21. 25 Jun, 2019 1 commit
  22. 15 May, 2019 1 commit
  23. 08 May, 2019 1 commit
  24. 04 Mar, 2019 1 commit
  25. 06 Feb, 2019 1 commit
  26. 22 Jan, 2019 1 commit
  27. 14 Dec, 2018 1 commit
  28. 11 Dec, 2018 1 commit
  29. 30 Oct, 2018 1 commit
  30. 02 Oct, 2018 1 commit
  31. 04 Sep, 2018 1 commit
  32. 22 Jun, 2018 2 commits
  33. 11 Jun, 2018 1 commit
  34. 07 Jun, 2018 2 commits
    • Christian Kuhn's avatar
      [TASK] Align impexp functional export tests between db engines · 965c6515
      Christian Kuhn authored and Wouter Wolters's avatar Wouter Wolters committed
      The ext:impexp related functional export tests compare
      with different target .xml file exports depending on
      the used db engine. This is ugly and pain to maintain.
      
      The patch aligns last differences between the generated
      exports by fixing sorting bugs in fixture db rows and adding
      an explicit order by at test preparation stage.
      Additionally, a column type bug in irre_tutorial fixture
      extension got resolved.
      
      The different .xml export file comparison fixtures per
      db engine are then merged into one and the split logic
      within tests removed.
      
      Change-Id: I429d5127e09c3e3714edae938cb0bf796b3274fd
      Resolves: #85178
      Releases: master
      Reviewed-on: https://review.typo3.org/57141
      
      
      Reviewed-by: Anja Leichsenring's avatarAnja Leichsenring <aleichsenring@ab-softlab.de>
      Tested-by: Anja Leichsenring's avatarAnja Leichsenring <aleichsenring@ab-softlab.de>
      Reviewed-by: Wouter Wolters's avatarWouter Wolters <typo3@wouterwolters.nl>
      Tested-by: Wouter Wolters's avatarWouter Wolters <typo3@wouterwolters.nl>
      965c6515
    • Christian Kuhn's avatar
      [FEATURE] Auto create management DB fields from TCA ctrl · 7b2319ff
      Christian Kuhn authored and Benni Mack's avatar Benni Mack committed
      Adds a class that auto creates TYPO3 "management" related database
      columns and indexes based on TCA 'ctrl' information without having
      them specified in ext_tables.sql. The feature .rst file outlines
      field details.
      
      Goals:
      * Save extension developers time.
      * Less copy+paste issues and different general fields definitions.
      * Reduce number of boilerplate fields in ext_tables.sql.
      * Bring schema of management fields under core control.
      
      Non goals:
      * No full substitution of ext_tables.sql by TCA: "Business"
        fields from 'columns' are NOT created automatically. This
        would require further thoughts and code disentangling.
      * No new extension API.
      * No "migration" approach or similar.
      
      Notable patch details:
      * The patch is a revamped version of issue #81234 that has been
        abandoned. As requested in the review of #81234, the code now
        hooks in after ext_tables.sql has been parsed into the doctrine
        schema.
      * Field defintions of ext_tables.sql take precedence, auto fields
        are only added if ext_tables.sql does not define a column or index.
        This makes the patch fully backwards compatible.
      * No deprecation for obsolete field definitions in ext_tables.sql
        is logged.
      * Many core fields are aligned to a central definition and slightly
        change. For instance "uid" is now always an unsigned int.
      * Reduce all core's ext_tables.sql files as well as the functional
        testing related ext_tables.sql files down to the business fields
      * A relatively huge series of test adaptions: Especially the
        ext:impexp related functionals now create dumps with differently
        sorted fields - This is no problem during import.
      * Field t3_origuid of sys_file_reference has never been registered
        in TCA as ['ctrl']['origUid'], is thus unused and removed as obsolete.
      * The extension manager no longer applies possible destructive changes,
        it only adds missing columns and tables when loading / updating
        extensions. It however considers *all* ext_tables.sql files, not only
        the one the extension in question provides. See the important .rst
        file for details.
      
      Change-Id: I640a7c7da3b63bac21a71102f253aa2d1bef4391
      Resolves: #85160
      Related: #81234
      Releases: master
      Reviewed-on: https://review.typo3.org/57121
      
      
      Tested-by: default avatarTYPO3com <no-reply@typo3.com>
      Reviewed-by: Anja Leichsenring's avatarAnja Leichsenring <aleichsenring@ab-softlab.de>
      Tested-by: Anja Leichsenring's avatarAnja Leichsenring <aleichsenring@ab-softlab.de>
      Reviewed-by: Wouter Wolters's avatarWouter Wolters <typo3@wouterwolters.nl>
      Reviewed-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      Tested-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      7b2319ff
  35. 30 May, 2018 1 commit
  36. 25 Apr, 2018 1 commit