Re: Re: [issues] [binarycloud] #107: properties without a name in conf.xml
| Newsgroups | gmane.comp.lib.binarycloud.devel |
|---|---|
| Organization | Solutions Only |
| Message-ID | <4220A954.16164.17BBE70@localhost> |
On 25 Feb 2005 at 14:40, alex black wrote: > > I am new to binarycloud and I do experience troubles to get used to the > > custom on the discussion list: I take any post seriously. > > Don't take them as instructions! :) > > > Now, people say that a path must be unique; people say that having > > arrays > > in the conf_value in the database is a bad idea (I removed the type > > 'object' from the proposal already). > > Both of those things are perfectly correct. Here's why: > > -a path in your proposal is acting as a PK and thus must be unique. You're probably reading some other proposal. I've never suggested that the primary key is the path. IT IS NOT. It's clearly stated that the PK is conf_id, which is an integer. > -serialized PHP arrays in database tables is bad form. I agreed on that before. That's why I deleted the option to store Objects in conf. (Which is, btw, to my opinion a very powerfull option.) > however, in clearly stating your problem with the current file format > in a ticket (see, tickets rule!) you showed me exactly what you were > referring to. I see now the power of tickets. They get attention, eeh ? ;-)) > After all this argument about it, I frankly thing your design should be > used almost verbatim for lang and we should basically leave conf alone. > With PHP5 tools we can parse those xml files quickly and easily, and I > don't see conf as being the biggest thorn in our side right now. > > > So I created a ticket in response to the post that acknowledges the > > error > > in xml. What can I say? > > You can say you contributed a ticket which clarified the whole > discussion for me. > > At this point it would be best to stop the list discussion for a moment > so you have time to compress it into changes to the Proposal Draft. > When you're done revising that draft we should all look at it and > comment on it. Good point. Still don't have an answer on the questions: 1. Do we allow for arrays as conf_values ? 1a. If so, paths would be typical unique. 1b. If not, a path is not unique at all. 2. What's the final directory structure for builded workspaces (eg testsite); Or otherwise; where is the conf directory in the new structure ???? wim niemans _______________________________________________ dev mailing list dev-PnctHDZWAvB/Cz2I37pSEPZ4XP/[email protected] http://lists.binarycloud.com/mailman/listinfo/dev