Perhaps you should consider a different strategy that does not couple so tightly the SQL schema with the parameters.
Rather that having an object which tries to keep everything directly on the object, place many of those values in a dictionary and do (key, value) lookups on the dictionary rather expecting the key to be a property of the object itself. That way, additional values can be associated with the object without changing the underlying database schema. Richard On Jun 12, 2012, at 9:58 AM, Barry Warsaw wrote: > On Jun 12, 2012, at 08:01 AM, Richard Wackerbarth wrote: > >> Core will need to be provided a dictionary of items related to the >> configuration of the list infrastructure. The URL for subscriber account >> maintenance is one of those items. However, the contents of that field, or >> any of the others, and how they are derived, is outside the scope of "core". >> To core, these are just configuration constants. > > It does, and it's not difficult to add new variables, except for the nightmare > (currently ongoing) of migrating the SQLite schema. _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
