Bug 7728

Graphical SQL generates incorrect sql 23 May, 2022

mike S
02 January, 2022
Product: PowerBuilder Category: DataWindow
Version: 2019 R3 Build: 2728
Classification: Enhancement Publishing: Public
Priority: P4
Status: Closed Reason: RECORDED AS ENHANCEMENT
Appeon Product 23 May, 2022
#7
Hi Mike,

Thank you for submitting the ticket.  


We now acknowledge this ticket to be an enhancement request and will record and track it internally in our enhancement management system. At the same time, we are closing the ticket here because this support system is for handling standard support services but not for maintaining enhancement requests.  

Please note that despite its "Closed" status, you are welcome to come back here and leave further comments or query the relevant development progress on this ticket.  


Thanks,

Julie
Ken Guo @Appeon 16 February, 2022
#6
Hi Mike,

Thanks for reporting this problem and for your valuable suggestion. 

We will submit this ticket to our development to further analyze the issue. It will take some time to reach a conclusion. We will keep you updated!

Regards,
Ken
mike S 15 February, 2022
#5
An alternative to fixing this is to provide a modern text sql editor with automatically look ups of columns like sql server manager, TOAD and other sql editors already do.   And also provide an IDE option to allow me to have text/syntax as the DEFAULT option rather than have to always select the convert to syntax.  I would greatly prefer a decent text sql editor to anything being done one the graphical one due to all the limitations of the graphical sql.
Ken Guo @Appeon 15 February, 2022
#4
Hi Mike,  

I'm just touching base with you about this ticket.  

Did we provide you with enough information to resolve this issue?
Please let us know if there is something else to support you with.  

Regards,
Ken
Ken Guo @Appeon 04 January, 2022
#3
Hi Mike,

Thanks for submitting this issue.
It’s true that this issue has been in all PB versions. The reason why none of Sybase, SAP, and Appeon fixes it, I think, is because if we want to fix this issue thoroughly, we will have to change it on the design level.

At this moment for the consideration of stability, we are not planning to improve it either. Hope you can understand.

If you run into similar issues in the future, it’s suggested that you Convert to Syntax then correct SQL as the workaround.


Regards,
Ken
David Xiong @Appeon 02 January, 2022
#2
Hi Mike,

Thanks for reporting the problem. We are currently on holiday for the New Year's Day holiday with limited access to the resources needed and will further look into this issue and get back to you when we get back to the office on Tuesday January 4, 2022.

Regards,
David
mike S 02 January, 2022
#1
Graphical Join Bug.rtf (2158KB)

*Phenomenon:
graphical datawindow generates incorrect/buggy sql when using compound outerjoins 

*Reproduce Steps:
see attached

Remarks:
This bug has existed since ANSI standard outer join syntax was added to PB (version 8?) and has been reported to sybase, sap, and appeon.    

I believe simplification of the sql generation (no more right outer joins, and use JOINs instead of listing tables using commas) would help fix these problems since it is too many things for your engineers to try to get to work.  Just use LEFT outer joins, and full joins and full outer joins .

---
An alternative to fixing this is to provide a modern text sql editor with automatically look ups of columns like sql server manager, TOAD and other sql editors already do.   And also provide an IDE option to allow me to have text/syntax as the DEFAULT option rather than have to always select the convert to syntax.  I would greatly prefer a decent text sql editor to anything being done one the graphical one due to all the limitations of the graphical sql.
OS:
All
Platform:
Database Type:
Microsoft SQL Server
Database Version:
2017