Derby
  1. Derby
  2. DERBY-4578

Documentation: Developer's Guide topic on double-booting is mostly obsolete

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 10.5.3.0
    • Fix Version/s: 10.6.1.0
    • Component/s: Documentation
    • Labels:
      None

      Description

      The topic "Double-booting system behavior", http://db.apache.org/derby/docs/dev/devguide/cdevdvlp20458.html, mostly describes issues that come up if you use a JDK earlier than 1.4. Since such JDKs are no longer supported for Derby, the info about these issues should be removed. What needs to remain is that with the embedded driver, Derby DOES prevent two instances of Derby from booting the same file-system database.

      The problem doesn't exist with in-memory databases – the db doesn't exist outside the JVM, so multiple Derby instances could refer to an in-memory db with the same name, but they wouldn't be the same db. That needs to be said too.

      The last paragraph, to the effect that if more than one Derby instance needs to access the same database you should use the Network Server, can remain (with some edits).

      1. DERBY-4578-2.diff
        7 kB
        Kim Haase
      2. DERBY-4578.diff
        7 kB
        Kim Haase
      3. cdevdvlp20458.html
        5 kB
        Kim Haase
      4. cdevdvlp20458.html
        5 kB
        Kim Haase

        Activity

        Hide
        Kim Haase added a comment -

        Attaching DERBY-4578.diff and cdevdvlp20458.html, with updates to the "Double-booting system behavior" topic that make it current (I hope).

        Please let me know if changes are needed.

        Show
        Kim Haase added a comment - Attaching DERBY-4578 .diff and cdevdvlp20458.html, with updates to the "Double-booting system behavior" topic that make it current (I hope). Please let me know if changes are needed.
        Hide
        Dag H. Wanvik added a comment -

        Thanks for improving this, Kim! Just a small detail:

        > You can allow multiple Derby instances that need to access that database to connect to
        > the server.

        That would be "applications on multiple JVMs" that need access to that database, not "Derby instances".
        The server would host the (single) Derby instance allowed to boot the database.

        Show
        Dag H. Wanvik added a comment - Thanks for improving this, Kim! Just a small detail: > You can allow multiple Derby instances that need to access that database to connect to > the server. That would be "applications on multiple JVMs" that need access to that database, not "Derby instances". The server would host the (single) Derby instance allowed to boot the database.
        Hide
        Kim Haase added a comment -

        Thanks, Dag – I am easily confused about instances and JVMs. Here is another attempt (DERBY-4578-2.diff).

        Show
        Kim Haase added a comment - Thanks, Dag – I am easily confused about instances and JVMs. Here is another attempt ( DERBY-4578 -2.diff).
        Hide
        Kim Haase added a comment -

        I plan to commit this patch on Monday 3/12 unless I hear there are issues. Hope that's okay.

        Show
        Kim Haase added a comment - I plan to commit this patch on Monday 3/12 unless I hear there are issues. Hope that's okay.
        Hide
        Knut Anders Hatlen added a comment -

        Looks great, Kim! +1

        Show
        Knut Anders Hatlen added a comment - Looks great, Kim! +1
        Hide
        Kim Haase added a comment -

        Thanks, Knut!

        Committed patch DERBY-4578-2.diff to documentation trunk at revision 923243.

        Show
        Kim Haase added a comment - Thanks, Knut! Committed patch DERBY-4578 -2.diff to documentation trunk at revision 923243.
        Hide
        Kim Haase added a comment -

        Changes have appeared in Latest Alpha Manuals, so closing.

        Show
        Kim Haase added a comment - Changes have appeared in Latest Alpha Manuals, so closing.

          People

          • Assignee:
            Kim Haase
            Reporter:
            Kim Haase
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development