Hi guys. I might just chime in here, if I may...
On Fri, 2002-08-09 at 18:26, Andrej Falout wrote: > A. True. But our main job is to supply SAP DB for SAP customers. Anything else has >to be done by others interested in > SAP DB. > > Me: How do we do that if we can't even get your (SAP junta) acceptance in principal >for simplest things, that cannot > conflict with your primary goal in any way? I asked 3 times already about adding >functionality that would return > assigned value of SERIAL via SQLCA, but there was no answer... > I wonder: apart from occasional bug patch, was there any code accepted in SAP DB so >far? > Can you please consider standardizing feature proposals evaluation and approval >process? I don't know the official line, but my thought here is this: If you create an extension or patch that works, is useful to people, and make it available (online, on sf.net, wherever), there is a good chance it will be considered - on the priviso that it doesn't break existing functionality. If not, at least othes can build it in if they want it - regardless of the official distro. I've heard a lot of talk about things that would be nice (myself included occassionally), but so far, very little *feature enhancement* code has been put up. The single biggest thing that is slowing me from getting into it seriously is the testing of changes. Postgres has regression testing and so on for example, but with SAP DB, I don't *know* that my changes haven't broken something else. I'd like to be able to put up a patch and say, "Here you go: it does X, and it works" - but without a serious test suite / functionality test, that gets harder. So how does SAP evaluate changes? Is there an internal functionality test that can be made available? Do we need to write one? Just my 2c on the contribution issue. Richard. _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
