Skip to content
Snippets Groups Projects
  1. Dec 17, 2012
  2. Dec 14, 2012
  3. Nov 16, 2012
  4. Nov 01, 2012
  5. Oct 19, 2012
  6. Oct 02, 2012
  7. Sep 27, 2012
  8. Sep 18, 2012
  9. Sep 14, 2012
    • Jared Hancock's avatar
      Add chunked file data support · e51bb66f
      Jared Hancock authored
      This will remove the upper limit of BLOB sizes imposed by MySQL with the
      max_allowed_packet setting completely.
      
      This adds a new table %file_chunk which will contain the filedata in smaller
      chunks (256kB). It also includes a new class, AttachmentChunkedData, which
      will handle reading and writing the data, abstracting away the chunks.
      
      This is done by migrating data from the %file table to the %file_chunk
      table. One must beware that this must safely (the migration that is) plug
      into the both the live osTicket developers as well as the users doing a full
      upgrade from osTicket-1.6*. For this, the AttachmentFile::save method was
      patched to use the new AttachmentChunkedData class to write the attachment
      data to the database in chunks. That is, the migrater will use the new code
      on the major upgrade and bypass the filedata column of the %file table
      altogether. Therefore, the patch associated with this commit will not
      migrate any data for the major upgrade.
      
      For developers doing incremental upgrades, the patch included in this
      commit will transfer the data from the %file data to the new %file_chunk
      table by chunking it. As written, only the first 16MB of the attachment is
      migrated. This could easily be adjusted, but it seems like a reasonable
      limit for now.
      e51bb66f
  10. Sep 10, 2012
  11. Sep 03, 2012
  12. Aug 31, 2012
  13. Aug 30, 2012
  14. Aug 13, 2012
  15. Aug 11, 2012
  16. Aug 08, 2012
  17. Jul 30, 2012
  18. Jul 22, 2012
  19. Jul 21, 2012
  20. Jul 16, 2012
  21. Jul 09, 2012
  22. Jul 08, 2012
  23. Jul 07, 2012
    • Jared Hancock's avatar
      Add UPGRADING.txt file to describe post automated upgrade activities · 48c3d764
      Jared Hancock authored
      The upgrader can't (and shouldn't) do everything necessary to complete an
      upgrade. The adminsitrator will need to take care of a few extra tasks that
      are outlined in the UPGRADING.txt file. One of the items includes removing
      source code no longer used in the 1.7 codebase. A script is shipped (Unix
      only) that allows an administrator to automatically clean up all old source
      files that are no longer used.
      48c3d764
  24. Jul 02, 2012
Loading