Re: Needed: a tidy model for varying numbers of multiple numerical values (page number refs)?

First, thanks for the responses. Second, to answer the questions: 1. > - how would you like to handle (or not-handle) overlapping > ranges?  ("100 ..150, 120, 145-155") as above, in order, lowest number in range first 2. > - are ranges always specified the same way? (".." vs. "-") According

Re: Needed: a tidy model for varying numbers of multiple numerical values (page number refs)?

On Mon, Mar 9, 2009 at 5:02 AM, Tim Chase wrote: > > Dave E wrote: > > I have some data (page number references) that looks like this: > > > > 320, 387..90, 410, 500 > > > > or (sustituting numerical .. ranges for conventional dashes) > > > > 320, 387-90, 410, 500,

Re: Needed: a tidy model for varying numbers of multiple numerical values (page number refs)?

Dave E wrote: > I have some data (page number references) that looks like this: > > 320, 387..90, 410, 500 > > or (sustituting numerical .. ranges for conventional dashes) > > 320, 387-90, 410, 500, 634 > > I'd just like to know the most Django-esque way of creating a model > for these? > >

Needed: a tidy model for varying numbers of multiple numerical values (page number refs)?

I have some data (page number references) that looks like this: 320, 387..90, 410, 500 or (sustituting numerical .. ranges for conventional dashes) 320, 387-90, 410, 500, 634 I'd just like to know the most Django-esque way of creating a model for these? The requirements are: 1. they're all