2 Commits (72f1360dea6a50eb461d7c62774f334246e6b4a6)

Author	SHA1	Message	Date
Kirill Solomko	72f1360dea	TT#174405 actual_billing_profile fix billing_profile relation ... * the relation was incorrectly performed by the contract_id instead of billing_profile_id Change-Id: I34bd736ab8028d57d8ee69022b15711a6fc4bb1e (cherry picked from commit a3c70dca13)	4 years ago
Rene Krenn	d7f5c6c8b0	TT#38402 new billing mappings resultsets/relationships ... new resultsets: - "legacy_billing_mappings": fast virtual view listing a contract's billing mappings according to the legacy table layout. this is used by panel UI to present the mappings in the convenient, known way. - "actual_billing_profiles": a resultset for joining the fast(er) billing.v_actual_billing_profiles it is only used for filters involving the (actual) billing profile or its properties. - "contracts_billing_profile_network" - "contracts_billing_profile_network_schedule": resultsets for the new db tables. added for completeness, but not directly used by panel dbix code. modified resultsets/relationships: - "contract_fraud_events": makes use of the fast billing.v_actual_billing_profiles view. - "billing_networks", "billing_profiles" and "contracts": have their billing_mappings relationship replaced by the billing_mappings_view resultset keep compatibility with existing panel code (ie. input check logic). - "contracts": the legacy "actual_billing_mappings" relationship is removed permanetly. deprecated resultsets: - "actual_billing_mappings": this old virtualview is only kept for now to be able to run the billing_mapping_effective_start_time.t testcases. - "billing_mappings": not in use any more. Change-Id: Ica6d0e3f28873046047e0dc3636177a269fa4267	7 years ago