Elfyn McBratney <[EMAIL PROTECTED]> tapota :

> Hey,
>
> On Wed, Aug 25, 2004 at 11:11:15PM +0200, Mathieu Roy wrote:
>> Elfyn McBratney <[EMAIL PROTECTED]> tapota :
>> 
>> > Hello Mathieu,
>> >
>> > On Tue, Aug 24, 2004 at 07:28:04AM +0200, Mathieu Roy wrote:
>> >> Elfyn McBratney <[EMAIL PROTECTED]> tapota :
>> >> 
>> >> > Hello,
>> >> >
>> >> > Would there be any interest in adding table indexes to the Savane
>> >> > database?  This could bring a noticable performance increase on certain
>> >> > queries for large databases (like Savannah's).
>> >> >
>> >> > If there is interest, I can write up a more in-depth proposal with some
>> >> > actual figures and example indexes.
>> >> 
>> >> It's indeed interesting. If you can and want to do it, feel free to
>> >> make so. 
>> >
>> > I can and want to. :)
>> >
>> >> SQL improvements must be added within the files in sql/mysql + in
>> >> update/relnumber
>> >
>> > Should this be done on a branch, or done on HEAD?  (I'm thinking the
>> > prior, but I want to be sure.)
>> 
>> I'm not sure about the actual impact of the whole thing. If it is just
>> an improvement without any risk, it could be done on HEAD. If it can
>> broke the whole stuff, then it has to go on a branch.
>>
>> More generally: HEAD = minor improvements, bugfixes. Branches =
>> everything else.
>
> I don't forsee any breakage.  Worst case scenario, I commit a typo, and
> the build breaks. ;)
>
> I'm easy which ever way we go this (branch or HEAD).

If I were you, I would commit on the HEAD, since there's no risk to
end up with a difficult-to-recover-something-working situation.

Regards,

-- 
Mathieu Roy

  +---------------------------------------------------------------------+
  | General Homepage:           http://yeupou.coleumes.org/             |
  | Computing Homepage:         http://alberich.coleumes.org/           |
  | Not a native english speaker:                                       |
  |     http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english  |
  +---------------------------------------------------------------------+

Reply via email to