Hey,
I was getting a weird can't adapt error when saving a record.
Previous posts talked about charset conversions, unicode, etc...
The problem I had turned out to be trying to write an object reference
where I should have put the key value instead.
e.g.
rec["myfk"] = myObj
c
Michael napisał(a):
> Thanks Thomas... your shot in the dark hit it's mark for me :)
>
> I was suffering the same "can't adapt" psycopg2 error (worked fine
> with sqlite), but it was due to the exact reason you stated.
>
> Although your solution is probably better in the long run, another
> solu
On Tue, Nov 20, 2007 at 03:04:09PM -0600, Jeremy Dunck wrote:
>
> On Oct 26, 2007 2:47 AM, sandro dentella <[EMAIL PROTECTED]> wrote:
> ...
> >
> > once again I stumble into this problem. This time I gathered some
> > more
> > info so I describe them.
>
> http://groups.google.com/group/djang
Thanks Thomas... your shot in the dark hit it's mark for me :)
I was suffering the same "can't adapt" psycopg2 error (worked fine
with sqlite), but it was due to the exact reason you stated.
Although your solution is probably better in the long run, another
solution is to simply convert the resu
This is just a shot in the dark, but I just solved a similar problem
that just popped up for me.
I noticed that you are creating slugs for your object near where the
error happens. I had the exact same error happen when creating
slugified names. It turned out that I was calling the built-in
slu
OK, filed a ticket, but really I do not have any idea as what might be
"usable information" in this case, just copied what I posted here.
What makes me thinking there's a bug somewhere, is that the code works
for psycopg and sqlite3, but fails for psycopg2.
On 20 Lis, 22:06, "Jeremy Dunck" <[EMAI
"Can't adapt" is quite a vague error that psycopg2 issues.
Your issue is (apparently) something to do with encoding, and that's
different than Sandro's issue.
Please include more information, especially if you do decide to file a
ticket. I can't help with the info given so far...
On Nov 20, 200
On Oct 26, 2007 2:47 AM, sandro dentella <[EMAIL PROTECTED]> wrote:
...
>
> once again I stumble into this problem. This time I gathered some
> more
> info so I describe them.
http://groups.google.com/group/django-users/browse_thread/thread/091aa6c088f6c090
I understand you're running wsgi r
The problem in my case seems to be strictly related to psycopg2
backend. I tried with psycopg and it does not happens.
Should I file a ticket?
On 20 Lis, 10:17, Jarek Zgoda <[EMAIL PROTECTED]> wrote:
> I just started receiving the same problem when I try to save an object
> that has non-ASCII va
On Tue, Nov 20, 2007 at 01:17:50AM -0800, Jarek Zgoda wrote:
>
> I just started receiving the same problem when I try to save an object
> that has non-ASCII values in char field (the values are all properly
> decoded to unicode)> This seems related to psycopg2 backend, as I do
> not observe such
I just started receiving the same problem when I try to save an object
that has non-ASCII values in char field (the values are all properly
decoded to unicode)> This seems related to psycopg2 backend, as I do
not observe such behaviour on my dev server with sqlite3 backend. The
model is similar to
On 26 Set, 12:59, Sandro Dentella <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm meeting a weird problem in a django application.
> It works w/o any problem from my pc connecting remotely to my customer's
> apache but is not working inside the lan.
>
> I'm connecting from firefox/ubuntu they're
Hi,
I'm meeting a weird problem in a django application.
It works w/o any problem from my pc connecting remotely to my customer's
apache but is not working inside the lan.
I'm connecting from firefox/ubuntu they're connecting from firefox/XP.
the weird part is that:
1. they h
13 matches
Mail list logo
