On Dec 21, 3:33 am, madhav <[EMAIL PROTECTED]> wrote:
> I did it, but its not showing up the new field(which is "summary" in
> my case) in the Create Statement, nor is at the Alter table part.
That's expected behaviour for generic objects (sorry, that I didn't
mention this in my earlier post).
I did it, but its not showing up the new field(which is "summary" in
my case) in the Create Statement, nor is at the Alter table part.
On Dec 20, 7:47 pm, Rajesh Dhawan <[EMAIL PROTECTED]> wrote:
> On second thoughts, "sqlall" might be better since it prints out
> indexes, initial_data, etc:
>
>
On second thoughts, "sqlall" might be better since it prints out
indexes, initial_data, etc:
python manage.py sqlall
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, sen
Hi,
> And I am using a class called Book which will be having the summary
> field mentioned above. So to alter the Book model at the database
> level, i need to run the alter table for Book. I dont know the
> equivalent sql to create a generic relation column in the table.
Just run "python manag
as a part of using generic relations, i got struck up at one point,
where i need to run the sql to have a field:
summary = generic.GenericRelation(Summary)
where Summary is a class defined as:
class Summary(models.Model):
id = models.AutoField(primary_key=True)
content_type = models.Fore
5 matches
Mail list logo
