From: Christopher S. <che...@ya...> - 2003-08-27 00:03:12
|
--- Julian Fitzell <ju...@be...> wrote: > The nice thing about serializing it is that you can still ask for the > value of the config option and get back the array you always used to > get. The config interface can still get that array out, display it, let > you modify it, and serialize the modified array back in for the new value. > > I realize it's pretty unclean from a DB point of view and I'm not > suggesting it's necessarily the right way to go - it just seems like the > simplest way to maintain our nice simple config_api while letting us > move the data into a declarative storage format. I guess this poses a question: Does the Mantis team want to take the path of least resistance for now, and comeback to this later? What I mean is, fix the current config system to be more db friendly (revamping it), or patch it for now. Julian's right, serialize() would be a quick solution. But as he's already pointed out, its not very DB-friendly. Perhaps a target version should be set for a revamp of the config system (say, 0.2, or 0.3), and serialize() could be used for now... Chris Shaffer __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com |