php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #41400 affected_rows wrong
Submitted: 2007-05-15 15:30 UTC Modified: 2007-05-16 06:45 UTC
From: corinl at gmx dot de Assigned:
Status: Not a bug Package: MySQLi related
PHP Version: 5.2.2 OS: debian 686
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem:
9 + 15 = ?
Subscribe to this entry?

 
 [2007-05-15 15:30 UTC] corinl at gmx dot de
Description:
------------
executing the following code using direct php (with mysqli) or using phpmyadmin using the mysqli extension returns 2 affected rows. running it with php or phpmyadmin using mysql extension, returns 0 affected rows (which is correct!).

using mysql 5.0.41 server and 5.0.38 client libraries.

Reproduce code:
---------------
CREATE TABLE `user_infos` (
  `user_id` int(10) unsigned NOT NULL,
  `mails` tinyint(4) NOT NULL,
  `mails_trigger` enum('0','1') collate latin1_german1_ci NOT NULL,
  `book` enum('0','1') collate latin1_german1_ci NOT NULL,
  `gtag` tinyint(4) NOT NULL,
  `foto_comment` enum('0','1') collate latin1_german1_ci NOT NULL,
  `buchung` enum('0','1') collate latin1_german1_ci NOT NULL,
  `blog_comment` enum('0','1') collate latin1_german1_ci NOT NULL,
  `i_mail` tinyint(4) NOT NULL,
  `i_buddy` tinyint(4) NOT NULL,
  `i_tele` tinyint(3) unsigned NOT NULL,
  `i_lchat` tinyint(3) unsigned NOT NULL,
  `i_close` enum('0','1') collate latin1_german1_ci NOT NULL,
  `max_fotoalben` tinyint(3) unsigned NOT NULL,
  `max_fotoalben_fotos` int(10) unsigned NOT NULL,
  `events` enum('0','1') collate latin1_german1_ci NOT NULL,
  `contacts_look` enum('text','images') collate latin1_german1_ci NOT
NULL default 'images',
  PRIMARY KEY  (`user_id`),
  KEY `trigger_mails` (`mails_trigger`,`mails`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_german1_ci;

INSERT IGNORE INTO user_infos SET
user_id=1,mails=1,book='1',gtag=1,foto_comment='0',blog_comment='1',buchung='1',i_mail=4,i_buddy=11,i_tele=5,i_lchat=10,i_close='0',events='1';


Expected result:
----------------
affected_rows = 1 (first insert)
0 in the following inserts



Actual result:
--------------
always 2

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2007-05-16 06:45 UTC] georg@php.net
Can't repeat.

both mysqli_affected_rows and mysql_affected_rows call and return the same api function from libmysql.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Thu Mar 28 20:01:28 2024 UTC