Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-7261

DocumentStore: inconsistent behaviour for invalid Strings as document ID

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 1.40.0
    • Component/s: documentmk, mongomk, rdbmk
    • Labels:
      None

      Description

      • H2DB and Derby roundtrip any string
      • PostgreSQL rejects the invalid string early
      • DB2 and Oracle fail the same way as segment store (they persist the replacement character) (see OAK-5506)
      • MySQL and SQLServer fail the same way as DB2 and Oracle, but here it's the RDBDocumentStore's fault, because the ID column is binary, and we transform to byte sequences ourselves
      • Mongo claims it saved the document, but upon lookup, returns something with a different ID

      Note that due to how RDB reads work, the returned document has the ID that was requested, not what the DB actually contains.

       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                reschke Julian Reschke
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: