Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-5320

Add well-known SQL schema where SQL caches will "live" by default

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskConvert to sub-taskLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.1
    • Component/s: sql
    • Labels:
      None

      Description

      Considerations:
      1) Schema is always present and is never dropped
      2) If CacheConfiguration.sqlSchema is not specified explicitly, cache should reside in default schema.
      3) There should be a flag on cache configuration to allow fallback to previous behavior, when cache existed in separate schema equal to it's name.
      4) CREATE TABLE can only create objects in default schema. Throw exception otherwise. That is, this is OK:

      CREATE TABLE "default_schema".MyTable ...
      

      And this is not:

      CREATE TABLE "non_default_schema".MyTable ...
      

      Default schema name should be public. This is well-known name of default schema, and moreover it already exists in H2.

        Attachments

        Issue Links

          Activity

          $i18n.getText('security.level.explanation', $currentSelection) Viewable by All Users
          Cancel

            People

            • Assignee:
              vozerov Vladimir Ozerov Assign to me
              Reporter:
              vozerov Vladimir Ozerov

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment