On Fri, Aug 13, 2010 at 5:27 PM, Kevin Horn <[email protected]> wrote:
> I'm very skeptical of any idea which involves storing configuration > information in a database (RDBMS). In my experience this causes more > problems than it solves, especially as applications grow in size and > complexity. The biggest problem with this approach (in my opinion, at > least) is that once you start storing config info in a database, it becomes > _very_ difficult to version-control. In my experience this ends up causing > all kinds of nasty administrative problems down the road. Of course, that > begs the question, what to do instead? > Okay, now this issue is one I honestly had not considered. Asking such questions is a very good thing in this case then. I'm opposed to the idea of writing a text file, myself, because of the issues with guaranteeing exclusive access to that file for the duration of the write. This problem becomes even more important on Windows machines. However, what I would be more amenable to is an import/export function, along with a changelog table. This would provide an easy ability to copy config anywhere, along with the accountability of seeing who changed what value when. How about that? Would that make for a decent compromise? The only reason I would be against using setuptools (via entrypoints) is > that it _will_ be going away...eventually. However, this will likely take > quite a while, and the distribute package should provide a fallback in case > of future problems with the "official" setuptools release. So I think using > setuptools' entrypoints is probably fine for now, with the following > caveats: > Well, if it's going away, it's going away. I'll simply have to provide a path to help extension developers migrate forward. 1) there are a number of people who will not use any application that relies > on setuptools, so be prepared to listen to some people gripe > 2) be prepared for some pain when/if you ever need to change to whatever > the replacement for entrypoints ends up being > I think that both those points are more simply stated as "It doesn't matter what you do. You are going to make a very vocal group of developers and users upset. Get ready for it." I'd be willing to drop setuptools, but I do need something to provide equivalent functionality. The entrypoints of setuptools is the only popularly deployed/deployable item that I'm aware of. Options, before I start coding, would be well received. -- Michael J. Pedersen My IM IDs: Jabber/[email protected], ICQ/103345809, AIM/pedermj022171 Yahoo/pedermj2002, MSN/[email protected] -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
