As much as I hate to suggest it, this sounds like a good time to use XML. Store each report as XML (in a file, or in a database row), then use templates to render the data.
-Jeff On Feb 9, 3:24 pm, Dids <didierblanch...@gmail.com> wrote: > > This is extremely unlikely to work, not to mention very inefficient. > > Can you let us know why you want to do this - what's your use case? We > > might be able to suggest a better way of doing it. > > -- > > DR. > > Users define a set of data they're interested in. Give a mean to get > the data (script, sql ...). The system goes and get the data at > regular interval (save by date) > The user can then review the data (table, charts , trends etc...) > See it as a basic monitoring system where I currently have no idea > what data the users will be interested in. > > I guess I can skip the table cration for each entity but I'm worried > the code for data retrieval might get messy. Not to mention the > templates ... > > Thanks for your input. > > Dids, --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
