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 Re: [Apache Bloodhound] #280: Move multiproduct.model.ModelBase to dashboard plugin
Date Fri, 07 Dec 2012 08:58:22 GMT
#280: Move multiproduct.model.ModelBase to dashboard plugin
---------------------------+------------------------------------
  Reporter:  olemis        |      Owner:  franco
      Type:  enhancement   |     Status:  accepted
  Priority:  trivial       |  Milestone:
 Component:  multiproduct  |    Version:
Resolution:                |   Keywords:  database model testing
---------------------------+------------------------------------

Comment (by rjollos):

 I haven't seen the previous discussion in which it was decided to move
 common components to dashboard, but my initial impression is that it
 doesn't make much more sense to have them in dashboard than in
 multiproduct. I had a brief discussion about this with gjm this evening,
 and we both think it might make sense to move the components to a new
 `bloodhound_core` directory. I  also think that `ModelBase.py` should be
 in `model.py` rather than `db.py`. My understanding is that only the
 schema and environment upgrade hooks should be in `db.py`.

 I've committed the fixes for the test cases in r1418224. Thank you franco
 and olemis! I look forward to hearing your comments on these other issues.

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

Mime
View raw message