Here is the test case:
CREATE USER "one.two"
IDENTIFIED BY "one.two"
GO
ALTER USER "one.two" QUOTA 100M ON USERS
GO
GRANT UNLIMITED TABLESPACE TO "one.two"
GO
GRANT create session TO "one.two"
GO
GRANT create table TO "one.two"
GO
GRANT create view TO "one.two"
GO
GRANT create any trigger TO "one.two"
GO
GRANT create any procedure TO "one.two"
GO
GRANT create sequence TO "one.two"
GO
GRANT create synonym TO "one.two"
GO
CREATE TABLE "one.two"."t1" (
"c1" VARCHAR2(25) NULL
)
STORAGE( BUFFER_POOL DEFAULT )
PARALLEL( DEGREE DEFAULT )
GO
INSERT INTO "one.two"."t1"("c1")
VALUES('Test1')
GO
SELECT * FROM "one.two"."t1"
GO
Highlight the last select statement in a QA window and Click on "Execute Edit" . See
attached.
The result is an error trying to set the current schema.
The problem is that StatementParser.breakTableSchemaDatabaseServerPathWithQuotes is not taking in account that a schema name can have a dot. It then breaks the schema into schema and database components. The connection cannot be made since the schema name is now incomplete.
I pushed this issue to the Aqua Data Studio v20 release. The change affects all of the databases that use the table data editor. Some of them allow a dot in the schema and table name. The parser needs to be able to handle this scenario. This change will require a lot of testing since most of the databases use this parser.