At 4:10 PM -0800 10/31/01, Bill Adams wrote: >Paul DuBois wrote: > >> [snip] >> >> >Of all the methods suggested I like the look of the one above and will >> >try that one first. >> > >> >$count = $sth->fetchrow_array(); >> > >> >$rows = $sth->rows() >> >> Note that use of rows() to get the row count for a SELECT is deprecated >> in the DBI docs, which say that if you want to know the number of rows >> in a result set, fetch and count them. (The reason is that rows() >> just doesn't work at all for some database engines. On the other hand, >> it appears to work just fine for MySQL...) > >Yes, MySQL will return the number of rows you /will/ get en total. Informix, >Oracle, etc.. return the number of rows you have retrieved so far. > >This is a database implementation issue and not a DBI/DBD issue. >(PHP follows the >same results.) Therefore if you want your code to work across dbs, you should >not rely on the value of ->rows(). > >b.
I agree with all of that except that it's not a DBI/DBD issue. Because this is a db implementation issue, that makes it a DBI issue, because people seem to want to rely on rows(), even though it's deprecated for SELECT. --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
