hi, On Mon, Mar 12, 2012 at 09:51:43PM -0400, Dennis Lee Bieber wrote: > On Mon, 12 Mar 2012 22:14:27 +0100, Ervin Hegedüs <airw...@gmail.com> > declaimed the following in gmane.comp.python.django.user: > > > > Some promotion has few millions of records, different promotions have > > different format of codes, ... And general: I'm looking for an ultimate > > solution, and may be the next time every ListRecord will have different > > columns. > > > Strangely, your "ultimate solution" might mean implementing a DBMS > AS the application, rather than just USING a DBMS... > > That is: maintaining a data dictionary which contains "promotion > format", "promotion field", "field type", (maybe field position too, > along with fields to identify constraints on the valid values); [...]
yes, it's absolutely true. But :), I'm so far from there I implement full of these. It's no problem, I'm just looking for a good solution, first it could be enough to implement all() method (and filter()), and there is an important invariant: in my (all) cases, the different ListItems has an intersect of columns, I mean there are a few columns, which exists in all ListItems object. Any idea? Thanks: a. -- I � UTF-8 -- 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.
