docs: add taos_print_row desc

[qevolg]

Description

Add taos_print_row desc

Checklist

Please check the items in the checklist if applicable.

• Is the user manual updated?
• Are the test cases passed and automated?
• Is there no significant decrease in test coverage?

[gemini-code-assist]

Summary of Changes

Hello @qevolg, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the project's documentation by adding a detailed description for the taos_print_row function, which is crucial for developers working with C/C++ connectors. Concurrently, it updates existing C example programs to illustrate how this function can be integrated for debugging and logging purposes, alongside general code formatting refinements to maintain code quality.

Highlights

• Documentation for taos_print_row: Added comprehensive documentation for the taos_print_row function in both English and Chinese C/C++ connector reference guides, detailing its purpose, parameters, and return values.
• C Example Code Updates: Updated several C example files (query_data_demo.c, tmq_demo.c, with_reqid_demo.c in both c-ws-new and c directories) to include commented-out sections demonstrating the usage of taos_print_row for logging/debugging query results. These examples also introduce a buffer for output and switch from taos_field_count to taos_num_fields where applicable.
• Minor Formatting Improvements: Applied minor code formatting adjustments across several C example files, primarily related to fprintf calls, variable declarations, and ConsumerConfig initialization, to improve readability and consistency.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds documentation for the taos_print_row C API function and updates several C examples to demonstrate its usage. The documentation is clear and helpful.

My review focuses on the example code. I've identified a couple of areas for improvement:

1. Buffer Size: All updated examples use a fixed-size buffer for taos_print_row. This could lead to silent data truncation or buffer overflows if the formatted row exceeds the buffer size. Since the API doesn't provide a way to determine the required size, it's important to highlight this risk in the examples.
2. Performance: In the tmq_demo.c examples, field metadata is fetched inside a loop, which is inefficient. This should be done once outside the loop.

These are important points to ensure users adopt best practices from the examples. The rest of the changes, including API updates (taos_field_count to taos_num_fields) and formatting, look good.