On Fri, Aug 13, 2010 at 9:10 PM, Michael Pedersen <[email protected]>wrote:
> On Fri, Aug 13, 2010 at 6:07 PM, Kevin Horn <[email protected]> wrote: > >> Also, such an import/export system can become an albatross in and of >> itself. What happens when/if you need to change the schema for it? If you >> decide to stick with a DB, _please_ make whatever data schema is involved >> simple enough that it shouldn't need to be changed often (or at all), and >> then draw a very definite line in the sand, after which you absolutely >> refuse to change it. >> > > Well, the schema was going to be very easy: name/value pairs, with the > value always being a string. Conversion to real data would be done via > formencode. However, the whole database thing now seems like a bad idea, in > light of something else you've said: > > >> For myself, it's unlikely that I will ever willingly use any extension >> that depends on config info in a DB. A VCS repository, though...hmmm. You >> could definitely use a hg repo or something as a back end, though it >> wouldn't be as straightforward. We did something like this many moons ago >> with Docudo (which was never finished...mostly due to lack of interest, >> though SVN was probably not the best choice for the back end). >> > > Perfect. I can easily manage an Hg repository from inside the extension. > Installation becomes a simple case of "point your .ini file variable at the > location of the repository". Instant changelog, commits are atomic, etc. The > whole thing becomes almost trivial. Thank you for this idea! :) > You're welcome. I'm interested to see what you come up with. > Now it's time to get busy implementing. For the actual on disk format, I'm > thinking of using json. It's fast to parse, provides a few more native > object types than straight up ConfigParser, still plain text. What do you > think? Good, bad, indifferent? > My big beef was having the data in a non-text format. I've done enough admin work in my time that I have firm opinions that you should only need a text editor to fix things. JSON should be fine for this. It's easily readable by both humans and computers. Good luck! Kevin Horn -- 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.
