mysql_use_result(3)

✨ mysql_use_result — bestie edition ✨

okay so this is a page from the MariaDB Connector/C manual, and it's about mysql_use_result(3) 💖 literally the function you call when you want your result set unbuffered, no cap.

🎀 NAME 🎀

mysql_use_result — returns an unbuffered result set. that's the whole vibe. ✨

🌸 SYNOPSIS 🌸

#include <mysql.h>

MYSQL_RES * mysql_use_result(MYSQL * mysql);

🦋 DESCRIPTION 🦋

so here's the tea, bestie 🫖 — you use this to initiate the retrieval of a result set from the last query you ran with mysql_real_query() on that database connection.

and listen, you gotta pick one: either this function or mysql_store_result(3) — one of them, no skipping, fr fr. Because you literally can't pull the results of a query without one of them. and if you call neither?? the next query on that same database connection is gonna fail 😭 so don't do that to yourself.

💅 PARAMETERS 💅

• mysql — your connection identifier, aka the little guy you already made with mysql_init(3) and then actually hooked up with mysql_real_connect(3). she's your main character connection 👑

⭐ NOTES ⭐

okay important part, pay attention 🫶

mysql_use_result() does not transfer the entire result set. it's giving "streaming, not hoarding." and because of that, several functions like mysql_num_rows(3) or mysql_data_seek(3) cannot be used. so don't try, she will not be answering 💀

also, mysql_use_result() will block the current connection until all result sets are retrieved, or the result set gets released by mysql_free_result(3). so yeah, that connection is busy being booked and blessed until you're done with her 🧚

🔥 RETURN VALUE 🔥

returns an unbuffered result set, or NULL if an error occurred. (if you get NULL, that's your vibe check failing, sorry bestie 🙈)

🌈 SEE ALSO 🌈

• mysql_store_result(3)
• mysql_free_result(3)

Version 3.4 of the MariaDB Connector/C docs, babes — that's a wrap, go forth and retrieve your result sets responsibly, mwah 💖🎀✨