While Csongor Fagyal (I belive) is correct about current behavior, the DBI
documentation explicitly says that this will break:
Currently, a new hash reference is returned for each
row. This will change in the future to return the
same hash ref each time, so don't rely on the current
behaviour.
Since you probably need to make a copy anyway, I wouldn't bother to worry
about what DBI may or may not do after a connection is closed. Seems much
safer to just assume that DBI owns the hash, and whatever you want needs to
be copied out.
Well,
I think this depends on your code. IMHO if you do not make a new call
against DBI while you use this hashref, you are still safe. I don't
think DBI can destroy your has if you set a reference to it - it can
only "overwrite" it if you issue a new call.
But please correct me if I'm wrong! This is an important thing.
Regards,
- Csongor
ps: SQL, bigint, hugeint, enormousint
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
