You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (Jira)" <ji...@apache.org> on 2024/08/28 16:53:00 UTC

[jira] [Created] (CALCITE-6553) In server, several CREATE and DROP commands are incorrect if schema does not exist

Julian Hyde created CALCITE-6553:
------------------------------------

             Summary: In server, several CREATE and DROP commands are incorrect if schema does not exist
                 Key: CALCITE-6553
                 URL: https://issues.apache.org/jira/browse/CALCITE-6553
             Project: Calcite
          Issue Type: Improvement
            Reporter: Julian Hyde


In server, several CREATE and DROP commands are incorrect if schema does not exist. 

CALCITE-4535 started this work, but missed some edge cases. In CALCITE-6552 I made the {{schema}} method return a nullable {{CalciteSchema}} (null if the schema of the object to be created or dropped does not exist) and saw several places that were not correctly handling a null value. I added a TODO in {{ServerDdlExecutor.java}}, and a fix for this case would remove those TODOs.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)