Parse Engine So weak

[sxl-vay]

select count(1) from ( select id,create_time from uf_shxl_alldata) aaa
Just like this simple SQL with a nested subquery seems to be challenging for Sharding's parsing engine to recognize logical tables. The parsing capability of Sharding's parsing engine appears to require further enhancement.

[sxl-vay]

SELECT * FROM (SELECT * FROM t_order WHERE order_id = 1) o WHERE o.order_id = 1;

This SQL, as showcased in the official documentation, seems to be unparseable by the ShardingSphere parsing engine as well.

[zhuruixuan]

Please follow the template to ask questions

[sxl-vay]

Please follow the template to ask questions
I can't find the template.I think I have tell you details of the questions

[strongduanmu]

@sxl-vay You can click new issue, and then chose issue template.

[zhuruixuan]

@sxl-vay


After selecting the type of issue, you can click in and follow the template.

Please be sure to fill in the information according to the template so that we can help you faster

[sxl-vay]

I'm sorry,

here are some infomation of my issue：
version： 4.0.0-RC1
I use shardingsphere-jdbc

in the following picture:
I used a sub-query sql,
This statement should perform full table routing
bug actual it made a error: can not find owner from table.

In addition，In my project there a lots of complex query sql(Just like the dql sql described in the picture above

)，that Sharding standard parsing engine can not parse it.
and I used sharding-jdbc 4.0.0-RC1，and I cannot upgrade the version.
Can you provide a way or give some suggestions on how to enhance the standard SQL parsing engine

[github-actions]

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.