I have been tasked to write a SQL script utilizing the 6i API to transfer data from a 1.3.2 Repository to a 6i Repository.
I am dealing strictly with business functions (ELEMENT_TYPE_FOR = FUN). I successfully transferred the business functions, but did not transfer any of the multi-line text columns. Now I am trying to get that information over.
I have tried using the RMOTEXTP.ReadAll() and RMOTEXTP.WriteAll() functions that are in the 6i API, but the problem is the fundamental difference between the back-end where the data is stored. In the 1.3.2 version of the API, the correct function to use would have been the RMOTEXT.Open(), .Read(), .Write().
In the 1.3.2 repository, the base table is CDI_TEXT, which has four columns. In the 6i repository, the base table is I$RM_TEXT_LINES, which has an additional 5 columns, which changes the meaning of the multi-line text from an attribute of the function (as in the 1.3.2 repository), to a secondary access element type (as in the 6i Repository), with the primary access element being the function itself (one of the new columns, pac_ref).
I wrote a SQL script that moves the text, but when it is viewed in the 6i Designer tool, all of the formatting is lost. Any newline/carraige returns are represented as a solid block in the editor, rather than a newline carraige return actually being performed on the raw data.
If I use the Designer 1.3.2 GUI to pull up the multi-line text and copy it, then use the Designer 6i GUI to paste it in, the formatting remains as it should be.
What is the GUI doing to the text that I am obviously omitting in my SQL script? I used a 3rd party software tool called LoadRunner to view the actual code that is being executed while the GUI is running, but did not find any differences between what my code is trying to do and what the GUI code is doing.
Any thoughts/help with this is greatly appreciated.
Thanks in advance!
Nanci
I am dealing strictly with business functions (ELEMENT_TYPE_FOR = FUN). I successfully transferred the business functions, but did not transfer any of the multi-line text columns. Now I am trying to get that information over.
I have tried using the RMOTEXTP.ReadAll() and RMOTEXTP.WriteAll() functions that are in the 6i API, but the problem is the fundamental difference between the back-end where the data is stored. In the 1.3.2 version of the API, the correct function to use would have been the RMOTEXT.Open(), .Read(), .Write().
In the 1.3.2 repository, the base table is CDI_TEXT, which has four columns. In the 6i repository, the base table is I$RM_TEXT_LINES, which has an additional 5 columns, which changes the meaning of the multi-line text from an attribute of the function (as in the 1.3.2 repository), to a secondary access element type (as in the 6i Repository), with the primary access element being the function itself (one of the new columns, pac_ref).
I wrote a SQL script that moves the text, but when it is viewed in the 6i Designer tool, all of the formatting is lost. Any newline/carraige returns are represented as a solid block in the editor, rather than a newline carraige return actually being performed on the raw data.
If I use the Designer 1.3.2 GUI to pull up the multi-line text and copy it, then use the Designer 6i GUI to paste it in, the formatting remains as it should be.
What is the GUI doing to the text that I am obviously omitting in my SQL script? I used a 3rd party software tool called LoadRunner to view the actual code that is being executed while the GUI is running, but did not find any differences between what my code is trying to do and what the GUI code is doing.
Any thoughts/help with this is greatly appreciated.
Thanks in advance!
Nanci