- 20.9.3 C API Function Descriptions
- 20.9.3.1 mysql_affected_rows()
- 20.9.3.2 mysql_autocommit()
- 20.9.3.3 mysql_change_user()
- 20.9.3.4 mysql_character_set_name()
- 20.9.3.5 mysql_close()
- 20.9.3.6 mysql_commit()
- 20.9.3.7 mysql_connect()
- 20.9.3.8 mysql_create_db()
- 20.9.3.9 mysql_data_seek()
- 20.9.3.10 mysql_debug()
- 20.9.3.11 mysql_drop_db()
- 20.9.3.12 mysql_dump_debug_info()
- 20.9.3.13 mysql_eof()
- 20.9.3.14 mysql_errno()
- 20.9.3.15 mysql_error()
- 20.9.3.16 mysql_escape_string()
- 20.9.3.17 mysql_fetch_field()
- 20.9.3.18 mysql_fetch_field_direct()
- 20.9.3.19 mysql_fetch_fields()
- 20.9.3.20 mysql_fetch_lengths()
- 20.9.3.21 mysql_fetch_row()
- 20.9.3.22 mysql_field_count()
- 20.9.3.23 mysql_field_seek()
- 20.9.3.24 mysql_field_tell()
- 20.9.3.25 mysql_free_result()
- 20.9.3.26 mysql_get_character_set_info()
- 20.9.3.27 mysql_get_client_info()
- 20.9.3.28 mysql_get_client_version()
- 20.9.3.29 mysql_get_host_info()
- 20.9.3.30 mysql_get_proto_info()
- 20.9.3.31 mysql_get_server_info()
- 20.9.3.32 mysql_get_server_version()
- 20.9.3.33 mysql_get_ssl_cipher()
- 20.9.3.34 mysql_hex_string()
- 20.9.3.35 mysql_info()
- 20.9.3.36 mysql_init()
- 20.9.3.37 mysql_insert_id()
- 20.9.3.38 mysql_kill()
- 20.9.3.39 mysql_library_end()
- 20.9.3.40 mysql_library_init()
- 20.9.3.41 mysql_list_dbs()
- 20.9.3.42 mysql_list_fields()
- 20.9.3.43 mysql_list_processes()
- 20.9.3.44 mysql_list_tables()
- 20.9.3.45 mysql_more_results()
- 20.9.3.46 mysql_next_result()
- 20.9.3.47 mysql_num_fields()
- 20.9.3.48 mysql_num_rows()
- 20.9.3.49 mysql_options()
- 20.9.3.50 mysql_ping()
- 20.9.3.51 mysql_query()
- 20.9.3.52 mysql_real_connect()
- 20.9.3.53 mysql_real_escape_string()
- 20.9.3.54 mysql_real_query()
- 20.9.3.55 mysql_refresh()
- 20.9.3.56 mysql_reload()
- 20.9.3.57 mysql_rollback()
- 20.9.3.58 mysql_row_seek()
- 20.9.3.59 mysql_row_tell()
- 20.9.3.60 mysql_select_db()
- 20.9.3.61 mysql_set_character_set()
- 20.9.3.62 mysql_set_local_infile_default()
- 20.9.3.63 mysql_set_local_infile_handler()
- 20.9.3.64 mysql_set_server_option()
- 20.9.3.65 mysql_shutdown()
- 20.9.3.66 mysql_sqlstate()
- 20.9.3.67 mysql_ssl_set()
- 20.9.3.68 mysql_stat()
- 20.9.3.69 mysql_store_result()
- 20.9.3.70 mysql_thread_id()
- 20.9.3.71 mysql_use_result()
- 20.9.3.72 mysql_warning_count()
unsigned long *mysql_fetch_lengths(MYSQL_RES
*result)
Description
Returns the lengths of the columns of the current row within a
result set. If you plan to copy field values, this length
information is also useful for optimization, because you can
avoid calling strlen(). In addition, if the
result set contains binary data, you
must use this function to
determine the size of the data, because
strlen() returns incorrect results for any
field containing null characters.
The length for empty columns and for columns containing
NULL values is zero. To see how to
distinguish these two cases, see the description for
mysql_fetch_row().
Return Values
An array of unsigned long integers representing the size of each
column (not including any terminating null characters).
NULL if an error occurred.
Errors
mysql_fetch_lengths() is valid
only for the current row of the result set. It returns
NULL if you call it before calling
mysql_fetch_row() or after
retrieving all rows in the result.
Example
MYSQL_ROW row;
unsigned long *lengths;
unsigned int num_fields;
unsigned int i;
row = mysql_fetch_row(result);
if (row)
{
num_fields = mysql_num_fields(result);
lengths = mysql_fetch_lengths(result);
for(i = 0; i < num_fields; i++)
{
printf("Column %u is %lu bytes in length.\n",
i, lengths[i]);
}
}
User Comments
While the above example doesn't show it, it's probably a good idea to malloc() the lengths variable using lengths = malloc( sizeof( unsigned long ) * num_fields ) prior to packing your column lengths in, and free()'ing it after you're done with them.
I say 'probably' a good idea, because I'm honestly not sure. The MYSQL_RES type with mysql_store_result automatically allocated the memory.
No Jennifer, that's not necessary.
It appears that the mysql_fetch_lengths() returns a pointer to data inside 'result' - the memory is allocated and freed with 'result'.
My code is similar to the example and I haven't run into any problems.
malloc is definately not a good idea.
malloc acquires some memory and returns a pointer to that memory. The call to fetch_lengths is going to overwrite that pointer.
A subsequent call to free using the value now in the lengths stack variable is going to attempt to free some memory inside the result structure. Exactly what would happen then I can't be bothered to investigate. I think, stress think, that free will give up 'cos it won't recognize the address passed to it.
The bad news is the pointer to malloced memory has now gone walkies and a memory leak has been created - whoops <g>
Add your own comment.