|
0
|
1 =====================
|
|
|
2 What's new in 1.2.1
|
|
|
3 =====================
|
|
|
4
|
|
|
5 Switched to Subversion. Was going to do this for 1.3, but a
|
|
|
6 SourceForge CVS outage has forced the issue.
|
|
|
7
|
|
|
8 Mapped a lot of new 4.1 and 5.0 error codes to Python exceptions
|
|
|
9
|
|
|
10 Added an API call for mysql_set_character_set(charset) (MySQL > 5.0.7)
|
|
|
11
|
|
|
12 Added an API call for mysql_get_character_set_info() (MySQL > 5.0.10)
|
|
|
13
|
|
|
14 Revamped the build system. Edit site.cfg if necessary (probably not
|
|
|
15 in most cases)
|
|
|
16
|
|
|
17 Python-2.3 is now the minimum version.
|
|
|
18
|
|
|
19 Dropped support for mx.Datetime and stringtimes; always uses Python
|
|
|
20 datetime module now.
|
|
|
21
|
|
|
22 Improved unit tests
|
|
|
23
|
|
|
24 New connect() options:
|
|
|
25 * charset: sets character set, implies use_unicode
|
|
|
26 * sql_mode: sets SQL mode (i.e. ANSI, etc.; see MySQL docs)
|
|
|
27
|
|
|
28 When using MySQL-4.1 or newer, enables MULTI_STATEMENTS
|
|
|
29
|
|
|
30 When using MySQL-5.0 or newer, enables MULTI_RESULTS
|
|
|
31
|
|
|
32 When using MySQL-4.1 or newer, more detailed warning messages
|
|
|
33 are produced
|
|
|
34
|
|
|
35 SET columns returned as Python Set types; you can pass a Set as
|
|
|
36 a parameter to cursor.execute().
|
|
|
37
|
|
|
38 Support for the new MySQL-5.0 DECIMAL implementation
|
|
|
39
|
|
|
40 Support for Python Decimal type
|
|
|
41
|
|
|
42 Some use of weak references internally. Cursors no longer leak
|
|
|
43 if you don't close them. Connections still do, unfortunately.
|
|
|
44
|
|
|
45 ursor.fetchXXXDict() methods raise DeprecationWarning
|
|
|
46
|
|
|
47 cursor.begin() is making a brief reappearence.
|
|
|
48
|
|
|
49 cursor.callproc() now works, with some limitations.
|
|
|
50
|
