On 12/15/06, Stefan Meretz [EMAIL PROTECTED] wrote:
On 2006-12-13 22:38, Shannon -jj Behrens wrote:
My memory is that MySQLdb recently changed a bunch of stuff and that
it was a simple logic bug.
You mean, that just the entire logic is reversed?
This would explain, why reading is working
My memory is that MySQLdb recently changed a bunch of stuff and that
it was a simple logic bug. Here's the bug I filed:
http://sourceforge.net/tracker/index.php?func=detailaid=1592353group_id=22307atid=374932
On 12/13/06, Michael Bayer [EMAIL PROTECTED] wrote:
in fact its almost definitely a
On 11/12/06, Michael Bayer [EMAIL PROTECTED] wrote:
since create_engine deals with class constructors, i went with this
approach:
def get_cls_kwargs(cls):
return the full set of legal kwargs for the given cls
kw = []
for c in cls.__mro__:
cons = c.__init__
if
The following results in correct data going into and coming out of the
database, but the data in the database itself looks double encoded:
import MySQLdb
connection = MySQLdb.connect(host=fmapp03, user=foxmarks,
passwd='ChunkyBacon', db=users)
cursor =
On 11/7/06, Michael Bayer [EMAIL PROTECTED] wrote:
yeah, or use introspection to consume the args, i thought of that too.
i guess we can do that. of course i dont like having to go there but i
guess not a big deal.
as far as kwargs collisions, yeah, thats a potential issue too. but
the
On 11/3/06, Shannon -jj Behrens [EMAIL PROTECTED] wrote:
I'm using convert_unicode=True. Everything is fine as long as I'm the
one reading and writing the data. However, if I look at what's
actually being stored in the database, it's like the data has been
encoded twiced. If I switch
