. Sorry.
On Tuesday 08 November 2005 9:06 am, Dwight Altman wrote:
I suppose you could use "count( PDOStatement::fetchAll() )", but I
understand your amazement.
mysql_num_rows() is specific to MySQL. He wants a PDO version.
-Original Message-
From: Micah Stevens [mailto:[EM
post. Sorry.
> >>
> >>On Tuesday 08 November 2005 9:06 am, Dwight Altman wrote:
> >>>I suppose you could use "count( PDOStatement::fetchAll() )", but I
> >>>understand your amazement.
> >>>
> >>>mysql_num_rows() is spec
ment.
mysql_num_rows() is specific to MySQL. He wants a PDO version.
-Original Message-
From: Micah Stevens [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 08, 2005 10:51 AM
To: php-db@lists.php.net
Subject: Re: [PHP-DB] [PDO] Number of rows found by Select
mysql_num_rows()
On Tu
I
> > understand your amazement.
> >
> > mysql_num_rows() is specific to MySQL. He wants a PDO version.
> >
> > -Original Message-
> > From: Micah Stevens [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, November 08, 2005 10:51 AM
> > To: php-db@list
ion.
>
> -Original Message-
> From: Micah Stevens [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, November 08, 2005 10:51 AM
> To: php-db@lists.php.net
> Subject: Re: [PHP-DB] [PDO] Number of rows found by Select
>
>
>
> mysql_num_rows()
>
> On Tuesday 08 Novem
To: php-db@lists.php.net
Subject: Re: [PHP-DB] [PDO] Number of rows found by Select
mysql_num_rows()
On Tuesday 08 November 2005 5:17 am, Rob C wrote:
> What is the recommended way to find the number of rows found by a SELECT
> query? PDOStatement::rowCount() doesn't work with MySQL and is a b
mysql_num_rows()
On Tuesday 08 November 2005 5:17 am, Rob C wrote:
> What is the recommended way to find the number of rows found by a SELECT
> query? PDOStatement::rowCount() doesn't work with MySQL and is a bit
> of a hack anyway. Doing a COUNT(*) before the SELECT is very hackish -
> the da
What is the recommended way to find the number of rows found by a SELECT
query? PDOStatement::rowCount() doesn't work with MySQL and is a bit
of a hack anyway. Doing a COUNT(*) before the SELECT is very hackish -
the data could have changed and it's an extra query. What is there
that's better
