Ard Biesheuvel wrote:

>>p.s. We do need to start taking a little more care of BIGINT. I've just
>>read the warning on mysql_insert_id ;)
>
> No problem here. The PHP extension converts all values that cannot be
> represented accurately by either int or float to string.

Yep - but the MySQL guys don't have that convention, so simple
conversions may work differently. I'm just nit picking, but I really
only see this as something that a MySQL 'convert' would be using until
they find the correct way of doing it ;)

BDE used to have many things like this - under certain conditions it
returned the correct answer, but once you drifted slightly the function
failed - just as I understand the mysql use of this fails if multiple
users are hitting the same table depending on which version of MySQL
your ISP has running :)

As I said "Do we want to propagate bad practice". If you do the job
correctly in the first place it CAN'T fail ;) Can you list the
conditions under which your function will not produce the right answer?

--
Lester Caine
-----------------------------
L.S.Caine Electronic Services