Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-4428

Add proper delete mechanism for in-memory databases


    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s:
    • Fix Version/s:
    • Component/s: JDBC, Services, Store
    • Labels:


      The current mechanism for deleting in-memory databases isn't good enough, and a proper one must be added.
      It is also important to be able to delete in-memory databases, since they occupy valuable main memory that should be discarded when the database is no longer needed.

      I intend to implement the mechanism by using the JDBC connection URL:

      The connection attempt will throw an exception in any case, either because the request failed or because it succeeded.
      Reasons for a failure can be invalid user and/or password, lacking encryption attributes, or conflicting attributes.
      For the time being, only the database owner will be allowed to delete databases (note: do we have a way to control/limit in-memory database creation?)


        1. derby-4428-0a-preview_patch.diff
          58 kB
          Kristian Waagan
        2. derby-4428-1a-in_memory_specific_delete_code.diff
          5 kB
          Kristian Waagan
        3. derby-4428-1a-in_memory_specific_delete_code.stat
          0.1 kB
          Kristian Waagan
        4. derby-4428-1b-in_memory_specific_delete_code.diff
          8 kB
          Kristian Waagan
        5. derby-4428-2a-generic_db_drop.diff
          14 kB
          Kristian Waagan
        6. derby-4428-2b-generic_db_drop.diff
          15 kB
          Kristian Waagan
        7. derby-4428-3a-canonical_name_handling.diff
          6 kB
          Kristian Waagan
        8. derby-4428-3b-canonical_name_handling.diff
          5 kB
          Kristian Waagan

          Issue Links



              • Assignee:
                kristwaa Kristian Waagan
                kristwaa Kristian Waagan
              • Votes:
                0 Vote for this issue
                0 Start watching this issue


                • Created: