Maybe the problem is that you don't quite understand what models are for. If you just want to create a report from your SQL data you use the models to structure the data and define relationships, not to report it. You use the views and the templates to generate the actual report.
Does that make sense? -Tim On Sun, Feb 21, 2010 at 9:27 AM, Atamert Ölçgen <[email protected]> wrote: > On Sunday 21 February 2010 16:16:56 Amps wrote: > > ok i had read, but was unclear ... ok, now , i am not using admin > > module. > > but can we create a model in model.py which doesnt reflect any table/ > > columns in the database, but should reflect a report columns. > AFAIK no. > > A practical approach could be to create a normal model that points to a > normal > table and then save your analytic data on it. It doesn't matter whether the > data is coming from a Queryset or raw SQL, you can > MyModel.objects.create(**my_data) as long as you create a my_data dict for > each entry. (you don't even have to save via ORM, but it's safer) > > Perhaps we can help better if you tell us what **exactly** you are trying > to > achieve and why you need a tableless model. > > > -- > Saygılarımla, > Atamert Ölçgen > > -+- > --+ > +++ > > www.muhuk.com > [email protected] > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<django-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
