Postgres does not return 'affected rows' when doing a select statement.

Even though PEAR supports this functionality, it fails silently when using postgres.

I have used the db_num_rows() function instead to return the amount of rows returned.

CommentFileSizeAuthor
#1 _2drupal1.67 KBadrian
_0drupal742 bytesadrian

Comments

adrian’s picture

adrian commented
StatusFileSize
new _2drupal1.67 KB

Update patch to remove second occurance of db_affected_rows in user.module

According to Killes, the mysql manual states that it also should not return affected rows on a 'select' statement.

dries’s picture

dries commented

Committed to HEAD. Thanks.

Anonymous’s picture

(not verified) commented