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

   ## 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.4.1
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   ShardingSphere-Proxy   apache-shardingsphere-5.4.1-shardingsphere-proxy-bin
   ### Expected behavior
   create table sql
   `CREATE TABLE memberinfo ( id INT PRIMARY KEY, name VARCHAR(50), idcard 
VARCHAR(50), house_id VARCHAR(50),relation INT;`
   
   insert into sample data. 
   `insert into memberinfo (id, name, idcard, house_id, relation) values (1, 
'张三', '421106199901011234', "123456houseid", 1) ,(2, '李四', '42110619900101789', 
"123456houseid", 1)`
   
   query sql 
   `select house_id, relation, row_number() over (partition by house_id ORDER 
BY relation asc ) AS relation_index from memberinfo  where house_id = 
'123456houseid'`
   
   sharding-config
   
   
![image](https://github.com/apache/shardingsphere/assets/11003275/ae0e56d2-642e-457e-8fc9-2a65e958d5ad)
   
   ###expected result:  
   
![image](https://github.com/apache/shardingsphere/assets/11003275/406275f6-0302-4729-97e1-b4efdbed1482)
   
   ### Actual behavior 
   relation_xuhao coloum 1,1 is error.
   
![image](https://github.com/apache/shardingsphere/assets/11003275/ee97205e-4545-4c62-bede-50bf6d396e7d)
   
   
   expected result relation_index is 1,2.
   
![image](https://github.com/apache/shardingsphere/assets/11003275/710064c8-1bc2-429c-8940-04bc6882e2a6)
   
   ### Reason analyze (If you can)
   in postgrmaybe not support.
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule 
configuration, when exception occur etc.
   
   ### Example codes for reproduce this issue (such as a github link).
    in database: Postgresql   
    query sql  'select house_id, relation, row_number() over (partition by 
house_id ORDER BY relation asc ) AS relation_index from memberinfo  where 
house_id = '123456houseid''
   
   >  in Postgresql, function row_number() is not work 
   
   
   


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