[DOCS-1779] C++ Driver documentation is not very helpful. Created: 06/Aug/13 Updated: 11/Jan/17 Resolved: 07/Feb/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | drivers, ecosystem |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gerry F | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Days since reply: | 10 years, 28 weeks, 1 day ago | ||||||||||||
| Description |
|
Currently, the best documentation is the source code and the Doxygen comments. This doesn't cover when and when not to call certain functions. This also doesn't cover the thread strategy of the driver and how to integrate into an application that has existing threads. A simple workflow for some common cases would be very valuable, especially if it included actual functions. Common cases would likely be ETL, supporting a web page (persistent, but not permanent, connections with threads), and business analyst activity (ie, interactive query tool with multiple connections). |