http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=283 pierrick@koha-fr.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |paul.poulain@free.fr Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #2 from pierrick@koha-fr.org 2006-04-20 04:00 ------- I see Paul commited a fix on C4::Acquisitions::newbasket revision 1.2 on July 15, 2004 removing the FIXME warning there was a risk that two librarians would have the same basket number (because the sub was selecting MAX() FROM aqbasket without inserting any line). Now, we have a clean sub which insert a line in aqbasket and a retrieval of the inserted basket number using $dbh->{mysql_insertid}. The problem with $dbh->{mysql_insertid} is that it is obviously DBMS dependent. This is why DBI sub last_insert_id exists. There's a note in the Perl code saying that $dbh->last_insert_id always returns null. I've tested $dbh->last_insert_id(undef, undef, undef, undef) and it works fine for me with DBI 1.48 (March 2005) and DBD::mysql 2.9007 (April 2005). In my opinion, the only problem that remains is a dependance to MySQL. The bug described above is fixed in rel_2_2 and current HEAD. I move the bug to RESOLVED FIXED, and ask Paul to CLOSE the bug if he agrees with my explanation. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.