I hadn't tried the TEXT type. It works as far as not throwing any exceptions, I'm trying to look at the moved data now to see if it is correct. I also tried the encode() on each dictionary value that I was having trouble with, and it also worked without throwing exceptions. I could still see a bunch of backslashes in the moved data, though, so something's still not correct there.
Thanks for the tips, I'll play with it some more. I had seen the TEXT type before, but when I saw that it subclassed String, I didn't think it would be useful to me. Now I realize that the size constraints are a factor as well. Brian On 7/21/06, Michael Bayer <[EMAIL PROTECTED]> wrote: > postgres does support a TEXT datatype (which in SQLAlchemy is most > simply "String" with no length), have you tried that ? the binary > datatype is going to want an array of bytes....you probably want to > encode() a unicode string first in that case. > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
