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

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

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 10.5.3.0
    • 10.6.1.0
    • Documentation
    • 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).

      Attachments

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

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            chaase3 Camilla Haase
            chaase3 Camilla Haase
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment