Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 10.5.1.1
    • Fix Version/s: 10.5.1.1
    • Component/s: JDBC
    • Labels:
      None

      Description

      The community should agree on a name for the subSubProtocol for the in-memory back end. The name will be used in the connection URL, and it is the mechanism used to tell Derby to use the in-memory back end:
      jdbc:derby:subSubProtocol:dbName

      Two hot candidates are:
      o mem
      o memory

      The former is shorter, the latter is slightly more descriptive. If you have opinions on this, please post a comment.
      We should decide on this before we cut the branch for 10.5.

        Activity

        Gavin made changes -
        Workflow jira [ 12454273 ] Default workflow, editable Closed status [ 12801655 ]
        Myrna van Lunteren made changes -
        Affects Version/s 10.5.1.1 [ 12313771 ]
        Affects Version/s 10.5.0.0 [ 12313010 ]
        Fix Version/s 10.5.1.1 [ 12313771 ]
        Fix Version/s 10.5.0.0 [ 12313010 ]
        Kristian Waagan made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Resolution Fixed [ 1 ]
        Kristian Waagan made changes -
        Fix Version/s 10.5.0.0 [ 12313010 ]
        Component/s JDBC [ 11407 ]
        Kristian Waagan made changes -
        Field Original Value New Value
        Attachment derby-4084-1a-subSubProtocol_name.diff [ 12402127 ]
        Kristian Waagan created issue -

          People

          • Assignee:
            Unassigned
            Reporter:
            Kristian Waagan
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development