#333: Rely on ModelBase._get_schema to populate MultiProductSystem.SCHEMA -
after
#314
---------------------------+-----------------------
Reporter: olemis | Owner: gjm
Type: enhancement | Status: review
Priority: major | Milestone: Release 4
Component: multiproduct | Version:
Resolution: | Keywords: database
---------------------------+-----------------------
Changes (by olemis):
* status: accepted => review
* owner: olemis => gjm
Comment:
Two patches are needed to implement this feature . The
[https://bitbucket.org/olemis/bloodhound-
mq/raw/t333_mp_gen_schema/t333/t333_r1427886_schema_autoinc.diff first
one] deals with auto incremented (key) columns while generating table
schema from model meta-data . The [https://bitbucket.org/olemis
/bloodhound-
mq/raw/t333_mp_gen_schema/t333/t333_r1427886_mp_gen_schema.diff second
one] reuses `_get_schema` to calculate `SCHEMA` as stated in ticket
summary and description . Patches have to be applied in
[https://bitbucket.org/olemis/bloodhound-mq/raw/t333_mp_gen_schema/series
this order] .
After applying these tests behave as follows :
{{{
#!sh
$ python /path/to/bh/bloodhound_multiproduct/tests/model.py
.........
----------------------------------------------------------------------
Ran 9 tests in 0.138s
OK
}}}
Hence I'm forwarding this ticket for review .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/333#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
