When a new module is available, having a simple tool (that works) to manipulate the associated database could save a lot of time in experimenting/testing with it. Also, making the project user friendly should be a priority for the project. Openser has a lot of barriers for newbies (understanding the architecture, understanding the scriting language, understanding the modules and the dependencies). Spending an hour or two on a simple script that will let other play with the db in an easy way would be a plus for the project. If the project is user friendly, it means that it is more accessible, more users, more testers and in the end a more robust project. Just my 2c.
Regards, Ovidiu Sas On Fri, Jul 4, 2008 at 1:17 PM, Juha Heinanen <[EMAIL PROTECTED]> wrote: > Henning Westerholt writes: > > > sure, this would be a good thing. But i don't use this openserctl stuff at > > all, as for me its easier to just use SQL. If i introduce this, then i > > probably also need to maintain it.. And i rather want to invest my time at > > the moment in other areas of the server. > > i agree with henning. i never use openserdbctl to manage db table contents. > perhaps we should not support that at all. > > -- juha > > _______________________________________________ > Devel mailing list > Devel@lists.openser.org > http://lists.openser.org/cgi-bin/mailman/listinfo/devel > _______________________________________________ Devel mailing list Devel@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/devel
