On 8/7/06, Niran Babalola <[EMAIL PROTECTED]> wrote:
>
> "UnicodeEncodeError: 'latin-1' codec can't encode characters in
> position 75-76: ordinal not in range(256)"
This indicates your default database connection character set is
latin1. You can change this in your server configuration, or you c
Wade Leftwich wrote:
> Gábor Farkas wrote:
>> Niran Babalola wrote:
>>> I've been developing a Django application using SQLite, and now I'm
>>> trying to move over to MySQL and actually launch the site. The
>>> application is storing data from RSS/Atom feeds using Universal Feed
>>> Parser, which
Gábor Farkas wrote:
> Niran Babalola wrote:
> > I've been developing a Django application using SQLite, and now I'm
> > trying to move over to MySQL and actually launch the site. The
> > application is storing data from RSS/Atom feeds using Universal Feed
> > Parser, which uses unicode strings for
Niran Babalola wrote:
> I've been developing a Django application using SQLite, and now I'm
> trying to move over to MySQL and actually launch the site. The
> application is storing data from RSS/Atom feeds using Universal Feed
> Parser, which uses unicode strings for all its data. When I try to
>
On Tue, 2006-08-08 at 00:14 +, Niran Babalola wrote:
> I've been developing a Django application using SQLite, and now I'm
> trying to move over to MySQL and actually launch the site. The
> application is storing data from RSS/Atom feeds using Universal Feed
> Parser, which uses unicode string
I've been developing a Django application using SQLite, and now I'm
trying to move over to MySQL and actually launch the site. The
application is storing data from RSS/Atom feeds using Universal Feed
Parser, which uses unicode strings for all its data. When I try to
store information from a feed i
6 matches
Mail list logo
