Re: [Sqlalchemy-users] unicode parameters

2006-06-27 Thread Randall Smith
I take back everything. psycopg 2 installs as psycopg2 so there is no conflict with psycopg. Also SA check to see what's available and prefers psycopg2. All is good. Randall Randall Smith wrote: > I don't think SA should do anything about it, just pointing it out. I > can't switch to 2.0

Re: [Sqlalchemy-users] unicode parameters

2006-06-27 Thread Randall Smith
I don't think SA should do anything about it, just pointing it out. I can't switch to 2.0 because of breaking changes. I think it was a change from mx.DateTime to Python's datetime module. A positive move, but still breaking. Randall Michael Bayer wrote: > even the psycopg site now says, "p

Re: [Sqlalchemy-users] unicode parameters

2006-06-27 Thread Michael Bayer
even the psycopg site now says, "psycopg 2.0, the one you shall use". On Jun 27, 2006, at 3:34 PM, Randall Smith wrote: > I'm having the same problem with psycopg 1.1.18. I'm betting it's > psycopg. > > Randall > > Gambit wrote: >> Hey All, >> >> This really looks exactly like the unicode prob

Re: [Sqlalchemy-users] unicode parameters

2006-06-27 Thread Randall Smith
I'm having the same problem with psycopg 1.1.18. I'm betting it's psycopg. Randall Gambit wrote: > Hey All, > > This really looks exactly like the unicode problems I was having. >http://www.sqlalchemy.org/trac/ticket/86 > > Are you using psycopg1 or psycopg2? Tried convert_unicode? Test

Re: [Sqlalchemy-users] unicode parameters

2006-05-08 Thread Sean Cazzell
Dennis, FWIW, Your test script runs ok for me with sqlite and the latest svn trunk. You might want try running it with the trunk+PG. Sean On Mon, 2006-05-08 at 16:45 -0600, Dennis Muhlestein wrote: > On 5/8/06, Michael Bayer <[EMAIL PROTECTED]> wrote: > im not able to reproduce this p

Re: [Sqlalchemy-users] unicode parameters

2006-05-08 Thread Dennis Muhlestein
On 5/8/06, Michael Bayer <[EMAIL PROTECTED]> wrote: im not able to reproduce this problem, i can send unicode() intoget_by or SQL constructs directly no problem.  i also dontimmediately see anything that could cause it to construe a unicodestring as anything other than a literal value (unless the u

Re: [Sqlalchemy-users] unicode parameters

2006-05-08 Thread Michael Bayer
im not able to reproduce this problem, i can send unicode() into get_by or SQL constructs directly no problem. i also dont immediately see anything that could cause it to construe a unicode string as anything other than a literal value (unless the unicode() function on your end is being cl