10-23-2018, 08:42 AM
This was brought to my attention by a coreBOS user in the US who has made a lot of speed optimizations. From what I can see the optimization is that FetchRow does not return both numeric and column based results and, the real important one, is that FetchRow does not HTML encode the results, they are returned as they are in the database, this saves some considerable time, which in many cases you waste again by having to HTML decode the values.
The functionality is equivalent so it is an issue of knowing when you should use one option over the other.
The functionality is equivalent so it is an issue of knowing when you should use one option over the other.
Joe
TSolucio
TSolucio