HISTORY 2.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100
  1. =====================
  2. What's new in 1.2.2
  3. =====================
  4. The build system has been completely redone and should now build
  5. on Windows without any patching; uses setuptools.
  6. Added compatibility for Python 2.5, including support for with statement.
  7. connection.ping() now takes an optional boolean argument which can
  8. enable (or disable) automatic reconnection.
  9. Support returning SET columns as Python sets was removed due to an
  10. API bug in MySQL; corresponding test removed.
  11. Added a test for single-character CHAR columns.
  12. BLOB columns are now returned as Python strings instead of byte arrays.
  13. BINARY character columns are always returned as Python strings, and not
  14. unicode.
  15. Fixed a bug introduced in 1.2.1 where the new SHOW WARNINGS support broke
  16. SSCursor.
  17. Only encode the query (convert to a string) when it is a unicode instance;
  18. re-encoding encoded strings would break things.
  19. Make a deep copy of conv when connecting, since it can be modified.
  20. Added support for new VARCHAR and BIT column types.
  21. DBAPISet objects were broken, but nobody noticed.
  22. ========================
  23. What's new in 1.2.1_p2
  24. ========================
  25. There are some minor build fixes which probably only affect MySQL
  26. older than 4.0.
  27. If you had MySQL older than 4.1, the new charset and sql_mode
  28. parameters didn't work right. In fact, it was impossible to create
  29. a connection due to the charset problem.
  30. If you are using MySQL-4.1 or newer, there is no practical difference
  31. between 1.2.1 and 1.2.1_p2, and you don't need to upgrade.
  32. =====================
  33. What's new in 1.2.1
  34. =====================
  35. Switched to Subversion. Was going to do this for 1.3, but a
  36. SourceForge CVS outage has forced the issue.
  37. Mapped a lot of new 4.1 and 5.0 error codes to Python exceptions
  38. Added an API call for mysql_set_character_set(charset) (MySQL > 5.0.7)
  39. Added an API call for mysql_get_character_set_info() (MySQL > 5.0.10)
  40. Revamped the build system. Edit site.cfg if necessary (probably not
  41. in most cases)
  42. Python-2.3 is now the minimum version.
  43. Dropped support for mx.Datetime and stringtimes; always uses Python
  44. datetime module now.
  45. Improved unit tests
  46. New connect() options:
  47. * charset: sets character set, implies use_unicode
  48. * sql_mode: sets SQL mode (i.e. ANSI, etc.; see MySQL docs)
  49. When using MySQL-4.1 or newer, enables MULTI_STATEMENTS
  50. When using MySQL-5.0 or newer, enables MULTI_RESULTS
  51. When using MySQL-4.1 or newer, more detailed warning messages
  52. are produced
  53. SET columns returned as Python Set types; you can pass a Set as
  54. a parameter to cursor.execute().
  55. Support for the new MySQL-5.0 DECIMAL implementation
  56. Support for Python Decimal type
  57. Some use of weak references internally. Cursors no longer leak
  58. if you don't close them. Connections still do, unfortunately.
  59. ursor.fetchXXXDict() methods raise DeprecationWarning
  60. cursor.begin() is making a brief reappearence.
  61. cursor.callproc() now works, with some limitations.