Hi,
I'm having the same problem with r6980. As an example I used the same
model as richbodo:
models.py:
class Account(models.Model):
name = models.CharField(max_length=200)
class Box(models.Model):
account = models.ForeignKey(Account)
mac = models.CharField(max_length=50)
choic
On Fri, 2007-11-30 at 17:42 -0800, Matt wrote:
> Was this ever fixed? I'm still experiencing similar behavior in r6783.
> Thanks!
What are you doing to repeat the problem? Please provide a very short
example that demonstrates the issue (and see r6650).
Malcolm
--~--~-~--~~---
Was this ever fixed? I'm still experiencing similar behavior in r6783.
Thanks!
--Matt
On Nov 15, 4:55 pm, richbodo <[EMAIL PROTECTED]> wrote:
> ...
>
> Thanks. I switched to Postgres for now and everything works fine.
> I'll switch back in a few days and file a bug report if necessary.
--~--~--
On Thu, 2007-11-15 at 15:23 -0800, richbodo wrote:
>
> Perhaps someone can see the problem with my very simple model.
> (Summary of this email in: http://pastebin.com/m7fba5e2c)
>
> I just started using Django yesterday, I created a very simple model,
> and a corresponding application called "s
> This is a Django bug. Looks like I inadvertently introduced it in r6650.
> All the testing I did for that change apparently missed one case. I'll
> fix this later on today.
>
> The good news is that since you're using MySQL, no harm is done: the
> default MySQL storage engine doesn't support re
Perhaps someone can see the problem with my very simple model.
(Summary of this email in: http://pastebin.com/m7fba5e2c)
I just started using Django yesterday, I created a very simple model,
and a corresponding application called "stats" and database called
"gmon", with only three very small tab
6 matches
Mail list logo
