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
The SQL statement is as follows, where two tables are binding relationships:
SELECT
pd.id,pde.ewallet_order_id
FROM payment_dynamicaccountinfo pd
LEFT JOIN payment_dynamicaccountinfo_extra pde ON pd.id = pde.payment_dynamicaccountinfo_id
WHERE 1 = 1 AND pd.dynamic_date >= '2023-01-01 00:00:00'
The current version is 5.12, and I have checked the latest version, which also has this problem.
I looked at the source code because the tableNames attribute in the TablesContext class is of type HashSet, causing the order of the tables to change
The version I used before was 4.1.1, but it has been solved in this version.
The SQL statement is as follows, where two tables are binding relationships:
SELECT
pd.id,pde.ewallet_order_id
FROM payment_dynamicaccountinfo pd
LEFT JOIN payment_dynamicaccountinfo_extra pde ON pd.id = pde.payment_dynamicaccountinfo_id
WHERE 1 = 1 AND pd.dynamic_date >= '2023-01-01 00:00:00'
The current version is 5.12, and I have checked the latest version, which also has this problem.
I looked at the source code because the tableNames attribute in the TablesContext class is of type HashSet, causing the order of the tables to change
The version I used before was 4.1.1, but it has been solved in this version.
I found the previous related issues #866
The text was updated successfully, but these errors were encountered: