Dear gods of Stackoverflow

Let's say I have a mysql query that selects a large dataset:

$query = "SELECT col_1, col_2, ..., col_99 FROM big_table";

And I get a MySQLi result like so:

$result = $db->query($query);

But then instead of dealing with $result in this scope, I pass it to a function:

my_function($result);

And once inside my_function(), I iterate through each row in the result and do stuff:

function my_function($result) { while($row = $result->fetch_object()) { ... } }

Please help me understand the memory implications of this approach.

In other words, what does $result contain, and are there any pitfalls with passing it to a function? Should I consider passing $result by reference instead? For what it's worth, I won't be needing $result once my_function() is done with it.

Cheers from South Africa!

本文开发(php)相关术语:php代码审计工具 php开发工程师 移动开发者大会 移动互联网开发 web开发工程师 软件开发流程 软件开发工程师

代码区博客精选文章
分页:12
转载请注明
本文标题:What are the implications of memory for passing a MySQLi result to a function in ...
本站链接:https://www.codesec.net/view/610657.html


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 开发(php) | 评论(0) | 阅读(91)