Thank you all for your response.  I will try the encoding resolution.

Ana

On Dec 23, 1:29 am, SteveMc <[email protected]> wrote:
> The other reply was correct; it's a character encoding issue. Take a
> look athttp://www.postgresql.org/docs/8.3/static/multibyte.html- I
> suspect you will need to run initdb -E UTF8 to set the default
> character set for the postgres install. Alternatively that page
> instructs how to create a specific database with a character set.
> Running
>  $ psql -l
> will tell you what character sets your databases are using.
>
> On Dec 22, 9:14 pm, Ana <[email protected]> wrote:
>
> > Hello,
>
> > I migrated my MySQL tables to Postgres.  Generally, the migration was
> > fine with one exception.  I have a table researchproj that included
> > two foreign keys (institution_id and contact_id).  I received the
> > following error:
>
> > Caught an exception while rendering: ('ascii', u'Jorge Gir\xf3n', 9,
> > 10, 'ordinal not in range(128)')
>
> > when I tried to access the researchproj table through admin.  If I
> > delete the column contact_id, the error goes away.  If I add the
> > column back onto the table the error returns.  All the tables contain
> > data, although I created a test researchproj table with just one
> > tuple.  I've added, deleted and done acrobats trying to get the admin
> > to accept the column contact_id in the researchproj table.  I have
> > checked the sequence numbers for all tables, and also any referential
> > integrity issues with all the tables.  Can someone help?
>
> > Thanks,
>
> > Ana
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to