On 7/21/06, Michael Bayer <[EMAIL PROTECTED]> wrote: > i didnt think we supported an interface for mxODBC at this time > (since ive never heard of it). also i see youre using psycopg (which > works only with postgres?) ? whats the database setup exactly ?
Ahhh, sorry for the confusion. I'm importing data from an ODBC connection INTO postgres. SA is only being used on the PG database. I'm taking info from the ODBC cursor and having SA construct a new table in postgres. Then I extract data from ODBC, create a dictionary from a single resutl row and insert it into postgres. I've done this on many tables from the old dbase database, but the one I'm working with now has a few "memo" fields that contain data that psycopg2 seems to be choking on. It boils down to trying to add data from a very long (1000+ chars, I'd guess) unicode string into a Binary type field. Again, this has worked in other instances. I'm really at a loss as to where to even check for issues. When I get back to my office, I'll run a few more tests to try and locate the exact offending field (there are 4 I suspect) and get some more info. Brian ------------------------------------------------------------------------- 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
