susongyan opened a new issue, #25536:
URL: https://github.com/apache/shardingsphere/issues/25536

   ## Bug Report
   
   **For English only**, other languages will not accept.
   
   Before report a bug, make sure you have:
   
   - Searched open and closed [GitHub 
issues](https://github.com/apache/shardingsphere/issues).
   - Read documentation: [ShardingSphere 
Doc](https://shardingsphere.apache.org/document/current/en/overview).
   
   Please pay attention on issues you submitted, because we maybe need more 
details. 
   If no response anymore and we cannot reproduce it on current information, we 
will **close it**.
   
   Please answer these questions before submitting your issue. Thanks!
   
   ### Which version of ShardingSphere did you use?
   5.3.0
   
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   
   proxy
   
   ### Expected behavior
   using node typeorm  execute sql  success 
   
   ### Actual behavior
   got  feature_not_supported error
   
   ### Reason analyze (If you can)
   pg  when using node typeorm  ,  it'll  send  flush_command(H..S)  before 
execute sql;   but  proxy PostgreSQLCommandExecutorFactory not support this 
command
   
   ```java
   private static CommandExecutor getCommandExecutor(final 
PostgreSQLCommandPacketType commandPacketType, final PostgreSQLCommandPacket 
commandPacket, final ConnectionSession connectionSession,
                                                         final PortalContext 
portalContext) throws SQLException {
           switch (commandPacketType) {
               case SIMPLE_QUERY:
                   return new PostgreSQLComQueryExecutor(portalContext, 
(PostgreSQLComQueryPacket) commandPacket, connectionSession);
               case PARSE_COMMAND:
                   return new 
PostgreSQLComParseExecutor((PostgreSQLComParsePacket) commandPacket, 
connectionSession);
               case BIND_COMMAND:
                   return new PostgreSQLComBindExecutor(portalContext, 
(PostgreSQLComBindPacket) commandPacket, connectionSession);
               case DESCRIBE_COMMAND:
                   return new PostgreSQLComDescribeExecutor(portalContext, 
(PostgreSQLComDescribePacket) commandPacket, connectionSession);
               case EXECUTE_COMMAND:
                   return new PostgreSQLComExecuteExecutor(portalContext, 
(PostgreSQLComExecutePacket) commandPacket);
               case SYNC_COMMAND:
                   return new PostgreSQLComSyncExecutor(connectionSession);
               case CLOSE_COMMAND:
                   return new PostgreSQLComCloseExecutor(portalContext, 
(PostgreSQLComClosePacket) commandPacket, connectionSession);
               case TERMINATE:
                   return new PostgreSQLComTerminationExecutor();
               default:
                   return new PostgreSQLUnsupportedCommandExecutor();
           }
       }
   ```
   
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule 
configuration, when exception occur etc.
   
   use node typeorm to execute pg sql 
   
   ### Example codes for reproduce this issue (such as a github link).
   
   


-- 
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.

To unsubscribe, e-mail: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to