Re: DB oci8 numRows() and portability

On Sat, Jan 17, 2004 at 10:01:19AM +0100, Lukas Smith wrote: > > The reasons is that someone writes an app that is supposed to work with > multiple backends but they have their own custom fall back if numRows > fails. For example they could then just fetch the entire result set into > a buffer etc. And the likelyhood of that is??? It's far more likely that someone new to the package (or trying to port something to Oracle) will try to use the method without having portability turned on needlessly get an error. Even if someone has done what you said, their code already has the ability to handle the result of the method when it actually returns the number of rows, so their program would continue on the direct course rather than their own convoluted workaround. Either way, they wind up in the same place. --Dan -- T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y data intensive web and database programming http://www.AnalysisAndSolutions.com/ 4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409