liujuntao commented on issue #2860: Access Sharing-Proxy 4.0.0RC2 with navicat return null point exception for lack of scheam URL: https://github.com/apache/incubator-shardingsphere/issues/2860#issuecomment-521148171 re-Command-13] ShardingSphere-SQL - SQLStatement: SelectStatement(super=DMLStatement(super=AbstractSQLStatement(sqlSegments=[TableSegment(startIndex=63, stopIndex=88, name=COLUMNS, quoteCharacter=NONE, owner=Optional.of(org.apache.shardingsphere.core.parse.sql.segment.common.SchemaSegment@a80183), alias=Optional.absent()), ColumnSegment(startIndex=7, stopIndex=18, name=TABLE_SCHEMA, quoteCharacter=NONE, owner=Optional.absent()), ColumnSegment(startIndex=21, stopIndex=30, name=TABLE_NAME, quoteCharacter=NONE, owner=Optional.absent()), ColumnSegment(startIndex=33, stopIndex=43, name=COLUMN_NAME, quoteCharacter=NONE, owner=Optional.absent()), ColumnSegment(startIndex=46, stopIndex=56, name=COLUMN_TYPE, quoteCharacter=NONE, owner=Optional.absent()), ColumnSegment(startIndex=96, stopIndex=107, name=TABLE_SCHEMA, quoteCharacter=NONE, owner=Optional.absent()), ColumnSegment(startIndex=126, stopIndex=137, name=TABLE_SCHEMA, quoteCharacter=NONE, owner=Optional.absent()), ColumnSegment(startIndex=140, stopIndex=149, name=TABLE_NAME, quoteCharacter=NONE, owner=Optional.absent()), org.apache.shardingsphere.core.parse.sql.segment.dml.item.SelectItemsSegment@771c829, org.apache.shardingsphere.core.parse.sql.segment.dml.predicate.WhereSegment@30ceb677, org.apache.shardingsphere.core.parse.sql.segment.dml.order.OrderBySegment@3b14a8a6], tables=Tables(tables=[Table(name=COLUMNS, alias=Optional.absent())]), logicSQL=SELECT TABLE_SCHEMA, TABLE_NAME, COLUMN_NAME, COLUMN_TYPE FROM information_schema.COLUMNS WHERE TABLE_SCHEMA = 'db1' ORDER BY TABLE_SCHEMA, TABLE_NAME, parametersCount=0)), selectItems=org.apache.shardingsphere.core.parse.sql.segment.dml.item.SelectItemsSegment@771c829, where=Optional.of(org.apache.shardingsphere.core.parse.sql.segment.dml.predicate.WhereSegment@30ceb677), groupBy=Optional.absent(), orderBy=Optional.of(org.apache.shardingsphere.core.parse.sql.segment.dml.order.OrderBySegment@3b14a8a6)) [INFO ] 16:09:53.360 [ShardingSphere-Command-13] ShardingSphere-SQL - Actual SQL: ds_0 ::: SELECT TABLE_SCHEMA, TABLE_NAME, COLUMN_NAME, COLUMN_TYPE FROM information_schema.COLUMNS WHERE TABLE_SCHEMA = 'db1' ORDER BY TABLE_SCHEMA, TABLE_NAME [ERROR] 16:09:53.411 [ShardingSphere-Command-14] o.a.s.s.f.c.CommandExecutorTask - Exception occur: org.apache.shardingsphere.core.parse.exception.SQLParsingException: Cannot support multiple schemas in one SQL at org.apache.shardingsphere.core.parse.filler.impl.TableFiller.fill(TableFiller.java:42) at org.apache.shardingsphere.core.parse.filler.impl.TableFiller.fill(TableFiller.java:35) at org.apache.shardingsphere.core.parse.filler.SQLStatementFillerEngine.fill(SQLStatementFillerEngine.java:65) at org.apache.shardingsphere.core.parse.SQLParseEngine.parse(SQLParseEngine.java:64) at org.apache.shardingsphere.shardingproxy.backend.text.TextProtocolBackendHandlerFactory.newInstance(TextProtocolBackendHandlerFactory.java:66) at org.apache.shardingsphere.shardingproxy.frontend.mysql.command.query.text.query.MySQLComQueryPacketExecutor.<init>(MySQLComQueryPacketExecutor.java:64) at org.apache.shardingsphere.shardingproxy.frontend.mysql.command.MySQLCommandExecutorFactory.newInstance(MySQLCommandExecutorFactory.java:72) at org.apache.shardingsphere.shardingproxy.frontend.mysql.command.MySQLCommandExecuteEngine.getCommandExecutor(MySQLCommandExecuteEngine.java:60) at org.apache.shardingsphere.shardingproxy.frontend.command.CommandExecutorTask.executeCommand(CommandExecutorTask.java:85) at org.apache.shardingsphere.shardingproxy.frontend.command.CommandExecutorTask.run(CommandExecutorTask.java:66) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
