Re: #23214 [NEW]: mysql_insert_id - Never use the function "Blank"

On 15 Apr 2003, Andrew Lindeman wrote: > On Tue, 2003-04-15 at 00:31, Philip Olson wrote: > > On 14 Apr 2003, Andrew Lindeman wrote: > > > Is this really a bug? I think it's just a confused user, but I want to > > > be sure before making it bogus. > > > > It's hard to say and in some ways doesn't even matter > > because it appears his problem exists in 4.1.2 but > > doesn't in 4.3.0 so even if it was a bug, it's been > > fixed. Although, ideally if resource became optional > > fairly recently we'd have a <note> on when that > > happened, that would be standard procedure. So, you > > may want see if that's the case here ;) > > > > On a related note, here's a user comment found at > > php.net/mysql-insert-id > > > > "Note that if you have more than one database link > > open, you need to tell it which one you want the > > last insert ID for, MySQL won't guess." > > > > IF that's true then it'd be a phpdoc bug as the docs > > make it seem the most recent of the two connections > > would be used. I guess one of the ext/mysql guys would > > have to clarify. Also, in this scenerio, Stefan might > > be using two connections... > > > > Regards, > > Philip > > > > I was thinking it might be the last _opened_ connection, not the last > _used_ connection (could be wrong, but that sounds logical). However, > PHP version could be to blame also... BTW I also meant "opened" not "used". Regards, Philip