I make a lot of use of PHP and ODBC connections to the database, 99% of the time, I get it right and ensure I "Connect to Actinic" "make the fetch from Actinic" "close the ODBC connection" and finally "release the connection and free up the resource"
so that I can call small functions like "getPageUrl ( $productCode )" this opens, fetches, closes and releases the connection
Similar functions can call things like "getProductImage ( $productCode )"
Using this functionality, I can do away with duplicate pages, and create pages of links just by including the $productCode in a list. - much faster, much easier but . . .
Like I say, normally everything is fine, but today, with nested fetches (loops) and I have now closed the connection before I have actually finished it.
Are there an experts out there, that can advise "more efficient" ways of "connecting to actinic" at the beginning of the page, do anything I want throughout the page, and finally, "closing the connection" at the end of the page
kev
so that I can call small functions like "getPageUrl ( $productCode )" this opens, fetches, closes and releases the connection
Similar functions can call things like "getProductImage ( $productCode )"
Using this functionality, I can do away with duplicate pages, and create pages of links just by including the $productCode in a list. - much faster, much easier but . . .
Like I say, normally everything is fine, but today, with nested fetches (loops) and I have now closed the connection before I have actually finished it.
Are there an experts out there, that can advise "more efficient" ways of "connecting to actinic" at the beginning of the page, do anything I want throughout the page, and finally, "closing the connection" at the end of the page
kev
Comment