On Oct 30, 7:27 am, "Diez B. Roggisch" <de...@nospam.web.de> wrote: [snip] > Or even better, by > not doing it at all - because usually, your datamodel is tied to your > program, so the need for this kind of dynamicity shouldn't arise in the > first place. > > Die
Perhaps that is true in the majority of cases, but there are exceptions. I can think of a couple of instances where one might need to do it: 1) A general database exploration or visualization application, or 2) Where one needs to perform a similar operation on several different tables. In a current case of mine, I'm converting from several externally provided tab-delimited tables to an in-memory sqlite database. Most of my app is tied closely to the model, and needs no such dynamicity. However, I want to automate the conversion, so I don't have to write 20 or so similar functions. -- http://mail.python.org/mailman/listinfo/python-list