On Tue, Jun 21, 2011 at 8:43 PM, Ramiro Morales wrote:
> That's what [1]ticket 11665 reports.
So it does! I'd just hit the problem when I wrote my mail, and hadn't
checked Trac yet.
I guess I'll apply the patch and see if it solves my problem tomorrow.
Thanks
Peter
--
You received this mess
On Tue, Jun 21, 2011 at 12:48 PM, Peter Russell wrote:
> I've just been writing a test which checks that a delete() method
> works correctly. The test passes, but on closer inspection it should
> have failed, because creating my object creates a second object which
> is not being deleted. In pri
I have a different problem, but the solution to both might be the same.
We use a lot of ForeignKeyFields with on_delete=models.DO_NOTHING,
since we found the default cascade behaviour dangerous (it was too
easy for one ill thought through delete to take out half the
database).
I've just been writ
On Mon, Jun 20, 2011 at 10:57 PM, Benedict Holland
wrote:
> I ran into a problem with running unit tests against views where it
> said that:
>
> HINT: Truncate table "challenges_challenge_attachments" at the same
> time, or use TRUNCATE ... CASCADE.
>
> I patched it to be this, only for postgresq
I ran into a problem with running unit tests against views where it
said that:
HINT: Truncate table "challenges_challenge_attachments" at the same
time, or use TRUNCATE ... CASCADE.
I patched it to be this, only for postgresql. This patch seems to work
quite well. I don't know if there are any p
