Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA |
|
| Priority | Low |
| Complexity | Unknown |
| Component | App - Visual Editing |
| Version | 13.0 |
|
1 KB
|
|
104 KB
We never modify the data that comes back from the database. The source of the procedure is stored and we extract and display it as is. It is possible that the display could be different on different platforms depending on what character set the database is using for line breaks and tabs and the sort but we still do not and will not modify database data.
Make sure to consider the option File->Options->SQL Editor->[Expand Tabs] option. Default is to expand tabs to spaces.
Make sure to consider the option File->Options->SQL Editor->[Expand Tabs] option. Default is to expand tabs to spaces.
From the screenshot, the tab loss is not the only problem. Everything is converted to uppercase, and spaces are added before and after a "." separating a fully qualified object.
Does this problem occur with ADS 12, 11, 10, 9?
From the screenshot, the tab loss is not the only problem. Everything is converted to uppercase, and spaces are added before and after a "." separating a fully qualified object.
Does this problem occur with ADS 12, 11, 10, 9?
If you execute below query, you can see that the Uppercase conversion and spaces before and after "." is done by the iSeries Server. We display exactly as what is stored in the SYSPROCS catalog table. This is the way we display in ADS 13, 12, 11 ....
SELECT ROUTINE_DEFINITION FROM QSYS2.SYSPROCS WHERE ROUTINE_SCHEMA = 'QTCP'
If you execute below query, you can see that the Uppercase conversion and spaces before and after "." is done by the iSeries Server. We display exactly as what is stored in the SYSPROCS catalog table. This is the way we display in ADS 13, 12, 11 ....
SELECT ROUTINE_DEFINITION FROM QSYS2.SYSPROCS WHERE ROUTINE_SCHEMA = 'QTCP'
from customer: Then I remembered Expand Tabs in options and it all made sense. As you guys discovered, iSeries performs some formatting on incoming SP text. One of the things it does is eliminate extra spaces. By Expanding Tabs I was changing the tabs into spaces, which were promptly discarded when I saved, resulting in the left-justified look. Thanks for your help.
from customer: Then I remembered Expand Tabs in options and it all made sense. As you guys discovered, iSeries performs some formatting on incoming SP text. One of the things it does is eliminate extra spaces. By Expanding Tabs I was changing the tabs into spaces, which were promptly discarded when I saved, resulting in the left-justified look. Thanks for your help.
Issue #9780 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| No fixed build |
| No time estimate |
We never modify the data that comes back from the database. The source of the procedure is stored and we extract and display it as is. It is possible that the display could be different on different platforms depending on what character set the database is using for line breaks and tabs and the sort but we still do not and will not modify database data.