Your message dated Mon, 27 Jul 2009 09:18:12 +0200
with message-id <[email protected]>
and subject line invalid bugreport
has caused the Debian Bug report #474580,
regarding python-mysqldb: Missing support for TEXT data type
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
474580: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=474580
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python-mysqldb
Version: 1.2.2-6
Severity: normal
MySQLdb seems to miss support for MySQL's data type TEXT. This crops up when
handling Unicode encoded strings.
TEXT seems to be similar to a BLOB though having textual features on sorting
and knows about encoding. [1]
The current behaviour towards TEXT data is to return it unencoded though
others seem to cover conversion (Unicode).
When option use_unicode is set to true MySQLdb will convert the following
for types according to the encoding: [2]
* FIELD_TYPE.STRING
* FIELD_TYPE.VAR_STRING
* FIELD_TYPE.VARCHAR
* FIELD_TYPE.BLOB
The field type definition [3] lacks an explicit definition of the TEXT type
and thus I assume further down in the implementation the case of TEXT
elements is not covered.
As I understand from the MySQL documentation [1] a BLOB shouldn't be
converted using some encoding though TEXT should be.
I couldn't find a place where the library asks about the actual data type
comming from MySQL but adding a new field type and adding it to the
conversion method doesn't do the trick. I guess this has to be fixed
upstream.
Christoph
[1] http://dev.mysql.com/doc/refman/5.0/en/blob.html
[2] /var/lib/python-support/python2.4/MySQLdb/connections.py
[3] /usr/share/python-support/python-mysqldb/MySQLdb/constants/FIELD_TYPE.py
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.22 (PREEMPT)
Locale: lang=de...@euro, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages python-mysqldb depends on:
ii libc6 2.7-10 GNU C Library: Shared libraries
ii libmysqlclient15off 5.0.51a-3 MySQL database client library
ii python 2.4.4-6 An interactive high-level object-o
ii python-support 0.7.7 automated rebuilding support for P
python-mysqldb recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
hello,
according to andy dustman (mysql-python upstream), this bugreport is
invalid. he writes:
TEXT and BLOB are the same field type in MySQL. The difference is the
BINARY flag and/or the character set (binary vs. anything else).
greetings,
jonas
--- End Message ---
_______________________________________________
Python-modules-team mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team
