Mercurial > p > mysql-python > mysqldb-2
annotate HISTORY @ 35:e7bd07afbcb9 MySQLdb
Conflict-filled merge from 1.2br for 558:559 set and exception fixes
author | kylev |
---|---|
date | Thu, 12 Feb 2009 00:23:41 +0000 |
parents | 0e37ee00beb7 |
children | d9bb912776a5 |
rev | line source |
---|---|
9
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
1 ===================== |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
2 What's new in 1.2.2 |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
3 ===================== |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
4 |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
5 The build system has been completely redone and should now build |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
6 on Windows without any patching; uses setuptools. |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
7 |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
8 Added compatibility for Python 2.5, including support for with statement. |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
9 |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
10 connection.ping() now takes an optional boolean argument which can |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
11 enable (or disable) automatic reconnection. |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
12 |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
13 Support returning SET columns as Python sets was removed due to an |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
14 API bug in MySQL; corresponding test removed. |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
15 |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
16 Added a test for single-character CHAR columns. |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
17 |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
18 BLOB columns are now returned as Python strings instead of byte arrays. |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
19 |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
20 BINARY character columns are always returned as Python strings, and not |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
21 unicode. |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
22 |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
23 Fixed a bug introduced in 1.2.1 where the new SHOW WARNINGS support broke |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
24 SSCursor. |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
25 |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
26 Only encode the query (convert to a string) when it is a unicode instance; |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
27 re-encoding encoded strings would break things. |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
28 |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
29 Make a deep copy of conv when connecting, since it can be modified. |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
30 |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
31 Added support for new VARCHAR and BIT column types. |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
32 |
0e37ee00beb7
Merge changes from 1.2 branch (r470:483): Mostly build-related.
adustman
parents:
3
diff
changeset
|
33 |
3 | 34 ======================== |
35 What's new in 1.2.1_p2 | |
36 ======================== | |
37 | |
38 There are some minor build fixes which probably only affect MySQL | |
39 older than 4.0. | |
40 | |
41 If you had MySQL older than 4.1, the new charset and sql_mode | |
42 parameters didn't work right. In fact, it was impossible to create | |
43 a connection due to the charset problem. | |
44 | |
45 If you are using MySQL-4.1 or newer, there is no practical difference | |
46 between 1.2.1 and 1.2.1_p2, and you don't need to upgrade. | |
47 | |
48 | |
49 ===================== | |
50 What's new in 1.2.1 | |
51 ===================== | |
52 | |
53 Switched to Subversion. Was going to do this for 1.3, but a | |
54 SourceForge CVS outage has forced the issue. | |
55 | |
56 Mapped a lot of new 4.1 and 5.0 error codes to Python exceptions | |
57 | |
58 Added an API call for mysql_set_character_set(charset) (MySQL > 5.0.7) | |
59 | |
60 Added an API call for mysql_get_character_set_info() (MySQL > 5.0.10) | |
61 | |
62 Revamped the build system. Edit site.cfg if necessary (probably not | |
63 in most cases) | |
64 | |
65 Python-2.3 is now the minimum version. | |
66 | |
67 Dropped support for mx.Datetime and stringtimes; always uses Python | |
68 datetime module now. | |
69 | |
70 Improved unit tests | |
71 | |
72 New connect() options: | |
73 * charset: sets character set, implies use_unicode | |
74 * sql_mode: sets SQL mode (i.e. ANSI, etc.; see MySQL docs) | |
75 | |
76 When using MySQL-4.1 or newer, enables MULTI_STATEMENTS | |
77 | |
78 When using MySQL-5.0 or newer, enables MULTI_RESULTS | |
79 | |
80 When using MySQL-4.1 or newer, more detailed warning messages | |
81 are produced | |
82 | |
83 SET columns returned as Python Set types; you can pass a Set as | |
84 a parameter to cursor.execute(). | |
85 | |
86 Support for the new MySQL-5.0 DECIMAL implementation | |
87 | |
88 Support for Python Decimal type | |
89 | |
90 Some use of weak references internally. Cursors no longer leak | |
91 if you don't close them. Connections still do, unfortunately. | |
92 | |
93 ursor.fetchXXXDict() methods raise DeprecationWarning | |
94 | |
95 cursor.begin() is making a brief reappearence. | |
96 | |
97 cursor.callproc() now works, with some limitations. | |
98 |