-
This is related to https://sourceforge.net/mailarchive/forum.php?thread_name=8519ac5b0704020012k1eaac058w50e84b12aa352f8c%40mail.gmail.com&forum_name=pymssql-users.
2009-04-30 18:16:25 UTC in Simple MS SQL Python extension module
-
See for example attached test case. Here, we attempt to drop
a non-existent table, which results in an exception (as
expected), and we continue on. Now we attempt to drop a view
by using "DROP TABLE". This also results in an expected exception.
However, after this point, any commits or rollbacks fail with
an error such as:
**************************************************
Traceback...
2009-04-30 18:15:37 UTC in Simple MS SQL Python extension module
-
debedb created the Open Discussion forum.
2009-03-05 19:52:22 UTC in Dbdb
-
Welcome to Open Discussion.
2009-03-05 19:52:22 UTC in Dbdb
-
> Currently there is no access to this field in MySQLdb-1.2. And even if
> there were, there is no sane way to fix the type conversion code to handle
> it. So this is a Won't Fix for MySQLdb-1.2.
Hm, wouldn't an equivalent of this fix in 1.2 be just replacing
if (mask & fields[i].flags) {
with
if (fields[i].charsetnr == 63) {
in _mysql_ResultObject_Initialize() in _mysql.c.
2009-03-05 03:04:01 UTC in MySQL for Python
-
Thanks, Andy - I got myself to the point of it setting a binary flag on a column with a _bin collation, I should have updated the ticket to save you some work. But once I got to that point I was wondering whether it is in fact not a MySQLdb but a MySQL bug - what is it doing setting BINARY flag.
2009-03-05 03:00:57 UTC in MySQL for Python
-
Here's the SHOW CREATE TABLE result:
CREATE TABLE `collatebug` (
`col` varchar(20) character set latin1 collate latin1_bin default NULL,
`nocol` varchar(20) default NULL
) ENGINE=MyISAM DEFAULT CHARSET=latin1
Here's what MySQL docs say:
"A non-binary string has a character set and is converted to another character set in many cases, even when the string has a _bin collation.".
2009-03-05 00:47:03 UTC in MySQL for Python
-
But that's just a collation, why would it have an impact on the actual data that's being returned. The character set is latin1 in both cases.
2009-03-04 23:58:44 UTC in MySQL for Python
-
This is using MySQLdb 1.2.2 with Python 2.5.
When I have a column defined as
foo varchar(20) character set latin1 collate latin1_bin
the value is returned as a str (not unicode) even when charset='utf8' is specified. However, if no collation is specified:
foo varchar(20) character set latin1
unicode is returned.
Attached is a simple script that shows how if collation is set, a...
2009-03-04 22:50:49 UTC in MySQL for Python
-
DECFLOAT type missing from SQL_type_dict (Type code: -360).
2009-02-20 00:45:20 UTC in PyDB2 - Python DB2 Interface And Tools
