Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bloodhound-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of olemis@gmail.com designates
 209.85.210.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAHM0gnjoR_zN-VcC+AGF3DBL+FWOndR1+xuurGHNXPtsfGX+0g@mail.gmail.com>
References: <053.a1c93bf3c7b64d42cbd51bc0db874012@incubator.apache.org>
	<068.75962d39ae5f84b27614bcf2e11bc737@incubator.apache.org>
	<CAGMZAuPNHMu8JPNYHpiWdXNy7mj09_XNjGiZuVwwStB75CivjQ@mail.gmail.com>
	<51274D17.6040707@digiverse.si>
	<CAGMZAuNgLehuYXJnpxWDsY2p9KgjaON5vB3Y_BZumnY8+8_CyQ@mail.gmail.com>
	<5127A104.50304@digiverse.si>
	<CAGMZAuNTwraW-oFpPefPjUPgo2zbMqUSZnBYE+6kYCZseVDEPA@mail.gmail.com>
	<512BA31C.2050101@digiverse.si>
	<CAGMZAuOJctdr56unKHcWnzgY2u5YUNhKnNN+6vff7U6GtRGt-g@mail.gmail.com>
	<512CC3D3.50408@digiverse.si>
	<CAGMZAuO3tOKM7GJnxLt=QMzn9m84jxp2Ypx6b5n4OqUU5NvR_Q@mail.gmail.com>
	<512E114B.3@digiverse.si>
	<CAGMZAuPF3W3qoy6RckeFj65x5GpaVCGu1+jAuYxhesAHnQ7BPg@mail.gmail.com>
	<CAHM0gnjoR_zN-VcC+AGF3DBL+FWOndR1+xuurGHNXPtsfGX+0g@mail.gmail.com>
Date: Wed, 27 Feb 2013 15:59:58 -0500
Message-ID: 
 <CAGMZAuOWdDMPTMBjpzEWtnOrORh8okVYqQA0WRqn59fTPQRg5g@mail.gmail.com>
Subject: Re: [Apache Bloodhound] #404: Populate default schema on product
 addition
From: Olemis Lang <olemis@gmail.com>
To: bloodhound-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On 2/27/13, Andrej Golcov <andrej@digiverse.si> wrote:
> Hi,
>

:)

> My suggestion is to start with supporting product column-based
> translation for known tables (for known and tested environment) and
> provide table-name-based translation for unknown tables (for unknown
> environment).
>

fwiw I'm just rethinking what we already have to achieve a more
consistent solution . I'm not hoping to get all this implemented for
Release 5 , though we really have to take care of improving O(p) table
number issue .

> When multiproduct feature is released, we can continue with future
> tuning of product column translation,  provide more testing and
> smoothly migrate tested plugins from table-name-based to more optimal
> solution. The migration can be performed more or less transparently
> for plugins.
>

ok .

> Yes, for the first phase, BH will not support 100+ products, but at
> least users can start to play with it. Otherwise, IMHO, we can spend
> months tuning the column-based solution and not having multi-product
> feature for a half of year.
>

fwiw +1 .
Nonetheless even if we stick to name prefix in Release 5 , IMO it's
really important to continue the discussion as we might come up with
something for Release 6 .

-- 
Regards,

Olemis.