Also, if you'd like to be a part of the future development of Team Coding (or any other features) within Toad, I'd highly recommend signing up for the beta program by clicking here: If you can wait a couple more weeks until Toad 12.9 is released, I think you'll be pleased to find the latest version a significant improvement over Toad 12.8. I tried your steps in Toad 12.9 and was not able to reproduce this issue. Team Coding has been completely rewritten in Toad 12.9 with a key focus on improved performance, stability, and usability. We're just about to release Toad 12.9 within the next couple of weeks. While Toad 12.8 did fix a number of issues within Team Coding from Toad 12.7, it still had a few issues and this may be one of them. If I can successfully fix this issue, maybe our boss would want me to fix other data issues.Īs stated in my previous message, once I have fixed all issues and resolved my time difference logic, I will update you.
I have come across other places in our student database with data issues. As such, I am assuming that the constraints, triggers, business rules, and data integrity you mentioned were maintained by the team that managed the program in my previous jobs but not being maintained in my current job. I will make appropriate changes to both the data set and the function and run them in our test environment to see the results.Įven though I do not have experience writing these functions/programs, I have worked with data sets that are very similar to this data in my previous jobs but without all the issues. Thank you again for creating unique time formats based on the data I shared, writing the function, and explaining it to me how it is going to work.
My rationale behind fixing this issue now is so that we do not have to go through the same issues next term when I have to submit these reports again. I have not only brought it to the concerned manager's attention, I have also made our boss (we both report to the same boss) aware of it. Let me respond to your last 3 messages in a bit more detail.
0 kommentar(er)
