incubator-bloodhound-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Bloodhound" <bloodhound-...@incubator.apache.org>
Subject [Apache Bloodhound] #288: Create prototype for legacy database schema proxy
Date Thu, 06 Dec 2012 08:31:34 GMT
#288: Create prototype for legacy database schema proxy
----------------------------------+--------------------
 Reporter:  jure                  |      Owner:  nobody
     Type:  enhancement           |     Status:  new
 Priority:  major                 |  Milestone:
Component:  multiproduct          |    Version:
 Keywords:  bep-003 multiproduct  |
----------------------------------+--------------------
 As discussed on the dev mailing list and documented in
 [https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0003#database-
 schema-changes], we want to make product a first class citizen in
 Bloodhound. This would be (as proposed) be implemented by introducing new
 column (product) to tables that hold per-product resources (milestones,
 components, versions,...). As this would break existing trac/plugin
 compatibility, the idea is to produce a database proxy component
 (prototype for starters) that would 'install' itself directly above the
 database, parse the SQL statements and modify them in such a way that
 would limit the scope (of the SQL statements) to the product in current
 scope. Using this approach (if it turns out to be feasible at all) we
 would keep compatibility with both trac and plugins and still be able to
 change the database schema as proposed and at the same time allow
 multiproduct aware code/plugins to leverage the new database schema.

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/288>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker

Mime
View raw message