This repository has been archived by the owner on Jan 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 5
/
CREDITS.txt
101 lines (71 loc) · 4.04 KB
/
CREDITS.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
MySQL++ was created by Kevin Atkinson during 1998. From version
1.0 (released in June 1999) through 1.7.9 (May 2001), the primary
maintainer was Sinisa Milivojevic <[email protected]>. Neither Kevin
nor Sinisa are currently involved in MySQL++ development. The current
maintainer is Warren Young <[email protected]>, starting with
version 1.7.10 in August of 2004.
For a fuller account of the library's history, see the first chapter
of the user manual. For the nitty-gritty details, see the ChangeLog
in the root package directory. ChangeLog items since 1.7.9 that
aren't attributed to anyone else were done by Warren Young.
Other contributors of note since 1.7.10:
Chris Frey <[email protected]>: Lots of GCC warning fixes
for the bleeding-edge compiler versions, Gentoo ebuild support,
and misc other fixes.
Mark Meredino <[email protected]>: Several fixes and
additions, including a lot of work on Microsoft Visual C++
compatibility, and discoveries made while spelunking in the
library.
Evan Wies <[email protected]>: Contributed several C++ code
style cleanups.
Arnon Jalon <[email protected]>: Added the multi-query
result set handling features, and examples/multiquery.cpp to
demonstrate it.
Korolyov Ilya has submitted several patches in many different
areas of the library.
Remi Collet <[email protected]> is maintaining offical RPMs
for Fedora, with other systems on the way. His work has improved
the RPM spec file we distribute greatly.
Joel Fielder <[email protected]> of Switchplane,
Ltd. created the ScopedConnection class, came up with the original
idea for Query's for_each() and store_in() methods, provided the
basis for examples/for_each.cpp, and provided a fix for exception
flag propagation in Query.
Jim Wallace <[email protected]> demonstrated the need
for BadQuery::errnum(), and contributed the patches and also
examples/deadlock.cpp to test that this feature does what it is
supposed to.
Jonathan Wakely <[email protected]> rebuilt my original versions
of ConnectionPool, RefCountedPointer, and RefCountedBuffer.
They're now simpler and safer. He also created the numeric
conversion logic in lib/mystring.h introduced in v3.0.
Adrian Cornish <[email protected]> Several fixes and
additions.
Rick Gutleber <[email protected]> contributed the
Query::insertfrom() method and associated InsertPolicy object,
as well as the SQLStream class.
Here are the personal credits from the old 1.7.9 documentation,
apparently written by Kevin Atkinson:
Chris Halverson - For helping me get it to compile under Solaris.
Fredric Fredricson - For a long talk about automatic conversions.
Michael Widenius - MySQL developer who has been very supportive of
my efforts.
Paul J. Lucas - For the original idea of treating the query object
like a stream.
Scott Barron - For helping me with the shared libraries.
Jools Enticknap - For giving me the Template Queries idea.
M. S. Sriram - For a detailed dission of how the Template Queries
should be implemented, the suggestion to throw exceptions on bad
queries, and the idea of having a back-end independent query
object (ie SQLQuery).
Sinisa Milivojevic - For becoming the new offical maintainer.
D. Hawkins and E. Loic for their autoconf + automake contribution.
See the ChangeLog for further credits, and details about the differences
between the many versions of this library.
Please do not email any of these people with general questions about
MySQL++. All of us who are still active in MySQL++ development read the
mailing list, so questions sent there do get to us:
http://lists.mysql.com/plusplus
The mailing list is superior to private email because the answers are
archived for future questioners to find, and because you are likely to
get answers from more people.