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

Valid statements rejected if Derby has not implicitly created the current user's schema.

    XMLWordPrintableJSON

Details

    • Normal
    • Repro attached
    • Seen in production

    Description

      There are many examples of statements failing because Derby has not implicitly created the schema associated with the current user. You don't see this if the schema is the default APP schema. But if the user is anyone other than APP, then various statements can fail. Maybe we should implicitly create a schema even if the user isn't APP. Right now, you get an error like this:

      ERROR 42Y07: Schema 'ROOT' does not exist

      The following script shows an example of this problem:

      connect 'jdbc:derby:memory:db;create=true;user=esq';

      create table licreq( domain varchar( 10 ) );

      connect 'jdbc:derby:memory:db;user=root';

      – fails
      ALTER TABLE esq.licreq ADD COLUMN u_domain GENERATED ALWAYS AS (UPPER(domain));

      connect 'jdbc:derby:memory:db;user=app';

      – succeeds
      ALTER TABLE esq.licreq ADD COLUMN u_domain GENERATED ALWAYS AS (UPPER(domain));

      Attachments

        1. d6361-ignore-missing-schema.diff
          5 kB
          Knut Anders Hatlen
        2. derby-6361-01-aa-createDefaultSchema.diff
          2 kB
          Richard N. Hillegas

        Issue Links

          Is contained by

          Bug - A problem which impairs or prevents the functions of the product. DERBY-6498 Derby does not always automatically create a user's schema

          • Major - Major loss of function.
          • Open
          is related to

          Task - A task that needs to be done. DERBY-6481 Derby 10.10 backport issue (winter/spring 2014)

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. DERBY-5139 User schema not auto-created on creation of self-referencing table

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. DERBY-3945 Generation clauses which mention user-coded functions may produce different resuls depending on who performs the triggering INSERT/UPDATE

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. DERBY-3270 Delayed (on-demand) creation of current user schema makes select from view belonging to other schema fail.

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              rhillegas Richard N. Hillegas
              rhillegas Richard N. Hillegas
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: