![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Where can I find the documentation for MySQL++? I'm using MS .NET. |
#3
| |||
| |||
|
|
Joachim Person wrote: Where can I find the documentation for MySQL++? I'm using MS .NET. The documentation is here: http://dev.mysql.com/doc/plusplus/en/index.html It's sadly out of date, but even for more than 20 minor version revs, very little in the API has really changed. If you skim the changelogs since 1.7.9 you'll see the changes. A couple of them are noteworthy, such as changes to filenames and a reversal of the exceptions, but most of the changes have been bug fixes, requested additions, etc. As a lover of documentation I'm thinking about taking this on as a project: To get this document up to date, and to improve chapter 5, which is the most useful but also the hardest to use. |
#4
| |||
| |||
|
|
As a professional writer and editor, I'd be happy to proofread a new version if you decide to take it on! |
#5
| |||
| |||
|
|
Steve Mansfield wrote: As a professional writer and editor, I'd be happy to proofread a new version if you decide to take it on! Actually, I think you could productively join the writing team. The perspective of a newbie can be valuable. And, as you may have discovered already, the best way to learn something is to try to teach it to someone else. It uncovers all those assumptions and gray areas in your knowledge, and you're forced to repair those holes as you go. |
#6
| |||
| |||
|
|
Indeed - as I go through the manual (which, on reflection, is really, *really* awful) I'm having a lot of those 'huh?' moments. Trouble is, at this stage I don't know whether those are caused by my lack of knowledge about C++ or just obscurity in the manual itself. |
|
So, if anyone on the writing team |

|
wants to send me the current version of the manual, |
#7
| |||
| |||
|
|
So, if anyone on the writing team wants to send me the current version of the manual, I'd be happy to go through it and mark up those points where I think 'WTF does this mean?' or 'tell me more...'. |
#8
| |||
| |||
|
|
I don't think anything should be done about the reference manual right now. I'll probably initiate that effort myself, using Doxygen or something like it: http://sourceforge.net/projects/doxygen/ |
|
So, if anyone on the writing team Um, so far, you and Earl are the team. Go team. ![]() |
#9
| |||
| |||
|
|
Steve Mansfield wrote: Indeed - as I go through the manual (which, on reflection, is really, *really* awful) I'm having a lot of those 'huh?' moments. Trouble is, at this stage I don't know whether those are caused by my lack of knowledge about C++ or just obscurity in the manual itself. The problem isn't that the manual is obscure, it's that it's a reference manual, not a tutorial. Sure, there's stuff in there that tries to be a tutorial, but they should be separated out and clarified. We should either have two manuals, or at least a manual in two sections. What a newbie wants from a manual is not the same thing that those of us who have been using MySQL++ for years want. |
#10
| |||
| |||
|
|
More specifically, the 'simple' example shows how to pull some rows from a table and print them. I managed to get this working without too much trouble, but then I look at the query object and see that it has a number of methods - query.store(), query.preview() and I immediately want to know what other methods there are, what types they return, what parameters, if any, they might take. In other words, a reference list of all the methods, properties, structures & types in the API would be very interesting. That way I can play around with them and learn by experience. |
|
I guess what I'm saying is that I need Chapter 5! And obviously the manual needs to be brought up to date by using the actual code from the examples. Lots of commenting in the code might help, too. |
![]() |
| Thread Tools | |
| Display Modes | |
| |