On Apr 18, 3:49 pm, Michaël Journo
wrote:
> Well you were right. The insert didn't return the id, so that was the
> problem.
>
> I used your trick (customizing the save method) and it seems to work
> just fine.
Glad it helped.
A mandatory warning: you are using non-public parts of Django's
backe
Well you were right. The insert didn't return the id, so that was the
problem.
I used your trick (customizing the save method) and it seems to work
just fine.
So thank you !
On 17 avr, 20:58, akaariai wrote:
> The problem seems to be that INSERT INTO partitioned_table values(...)
> RETURNING ID
The problem seems to be that INSERT INTO partitioned_table values(...)
RETURNING ID isn't for some reason returning the ID. Can you confirm
this is the case by running the insert query manually from dbshell?
I believe 1.3 used SELECT
currval(pg_get_serial_sequence('partitioned_table', 'id')) inste
Hello,
I use postgresql 9.1 with postgresql_psycopg2 on debian (actually this
also happens on my mac). I recently moved to django 1.4 and I got this
error while creating a simple object :
o = Object()
o.fieldA = ..
o.save()
Traceback (most recent call last):
File "", line 1, in
File "/op
4 matches
Mail list logo
