You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting a super type without the + character prefixing the super type fails, even though documented to work. However, given the + / - syntax, is the plain syntax even necessary? If so, this part could just be removed from the documentation.
<ArcadeDB_0> Error on command execution (PostCommandHandler)
com.arcadedb.exception.CommandSQLParsingException: ALTER TYPE sup SUPERTYPE doc
at com.arcadedb.query.sql.parser.StatementCache.throwParsingException(StatementCache.java:126)
at com.arcadedb.query.sql.parser.StatementCache.parse(StatementCache.java:116)
at com.arcadedb.query.sql.parser.StatementCache.get(StatementCache.java:70)
at com.arcadedb.query.sql.SQLQueryEngine.parse(SQLQueryEngine.java:207)
at com.arcadedb.query.sql.SQLQueryEngine.command(SQLQueryEngine.java:102)
at com.arcadedb.database.EmbeddedDatabase.command(EmbeddedDatabase.java:1250)
at com.arcadedb.server.ServerDatabase.command(ServerDatabase.java:416)
at com.arcadedb.server.http.handler.PostCommandHandler.executeCommand(PostCommandHandler.java:127)
at com.arcadedb.server.http.handler.PostCommandHandler.execute(PostCommandHandler.java:88)
at com.arcadedb.server.http.handler.DatabaseAbstractHandler.execute(DatabaseAbstractHandler.java:91)
at com.arcadedb.server.http.handler.AbstractHandler.handleRequest(AbstractHandler.java:128)
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:393)
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:859)
at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2513)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1538)
at org.xnio.XnioWorker$WorkerThreadFactory$1$1.run(XnioWorker.java:1282)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: com.arcadedb.query.sql.parser.ParseException: Encountered " <ALTER> "ALTER "" at line 1, column 1.
Was expecting one of:
<ALIGN> ...
<SELECT> ...
<TRAVERSE> ...
<MATCH> ...
<INSERT> ...
<RETURN> ...
<CHECK> ...
<BACKUP> ...
<REBUILD> ...
<EXPORT> ...
<IMPORT> ...
<BEGIN> ...
<COMMIT> ...
<ROLLBACK> ...
<IF> ...
<SLEEP> ...
<SELECT> ...
<SELECT> ...
<TRAVERSE> ...
<MATCH> ...
<INSERT> ...
at com.arcadedb.query.sql.parser.SqlParser.generateParseException(SqlParser.java:26917)
at com.arcadedb.query.sql.parser.SqlParser.jj_consume_token(SqlParser.java:26762)
at com.arcadedb.query.sql.parser.SqlParser.StatementInternal(SqlParser.java:1359)
at com.arcadedb.query.sql.parser.SqlParser.Statement(SqlParser.java:1004)
at com.arcadedb.query.sql.parser.SqlParser.Parse(SqlParser.java:245)
at com.arcadedb.query.sql.parser.StatementCache.parse(StatementCache.java:111)
... 16 more
Steps to reproduce
CREATE DOCUMENT TYPE doc;
CREATE DOCUMENT TYPE sup;
ALTER TYPE sup SUPERTYPE doc;
ArcadeDB Version: v23.1.2 (build 9dbe3ce/1675373316135/main)
JDK Version: openjdk 11.0.18 2023-01-17
OS: MacOS 12.6
Setting a super type without the
+character prefixing the super type fails, even though documented to work. However, given the+/-syntax, is the plain syntax even necessary? If so, this part could just be removed from the documentation.Expected behavior
Success
Actual behavior
Cannot execute command Encountered " <ALTER> "ALTER "" at line 1, column 1. Was expecting one of: <ALIGN> ... <SELECT> ... <TRAVERSE> ... <MATCH> ... <INSERT> ... <RETURN> ... <CHECK> ... <BACKUP> ... <REBUILD> ... <EXPORT> ... <IMPORT> ... <BEGIN> ... <COMMIT> ... <ROLLBACK> ... <IF> ... <SLEEP> ... <SELECT> ... <SELECT> ... <TRAVERSE> ... <MATCH> ... <INSERT> ...Details
Steps to reproduce
This works as expected: