On Tue, Aug 15, 2017 at 12:29 PM, Alan Gauld via Tutor <tutor@python.org> wrote: > On 15/08/17 15:09, Neil Cerutti wrote: > >>> There are a variety of reports that I would like to be able to >>> print to screen or paper. Things such as a "Top x List" of >>> rated players, full rating list sorted from highest rating to >>> lowest, rating lists for the current school year only or a >>> particular past school year, and so. ... > >> You really can do it, but to me this requirement argues for going >> back to a database backend. Why rewrite SQL?
I just thought this would be an interesting problem type to tackle. No intentions of reinventing SQL! > I agree with Neil, this is exactly what SQL is good for and > would make this part of the project much easier and would have > the added benefit of introducing you to one of the trickiest, > but most common, bits of OOP - object persistence... Would you expand on this in SQLite terms? > You might even find yourself writing some class methods! ;-) Nah. I might expand my array of constants, and test a few more ... ~(:>)) -- boB _______________________________________________ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: https://mail.python.org/mailman/listinfo/tutor
