2 Commits (05eb8f6ec146ed265d97332008fbce32d5302a51)

Author	SHA1	Message	Date
Rene Krenn	171d79210a	MT#20027 porting number history ... -undo unique lnp_numbers: undo misleading unique keys -retain lnp_provider delete cascade restriction -api: wire lnp_numbers_actual -lnpnumbers collection pagination request takes several seconds (up to tens of for 200k lnp numbers), too slow especially for GET /api/lnpnumbers/?number=.. lookups -query param is properly injected into the virtual view sql query, so the lookup is fast now. -panel UI custom datatable filter to switch between complete history (all records) and actual portings -"terminate" lnp number: DELETE /api/lnpnumbers/?number=x +special use-case for melita's crm +all empty or future "end" timestamps of records are set to now(), so a subsequent listing shows no records any more. -number parameter is forced, other collection query params are currently not supported for DELETE Change-Id: I7b69d16a2d4f38ea84fc1cc0b407fa67e0f5ef8b	9 years ago
Rene Krenn	2912808d77	MT#20023 MT#20027 lnp unique number and lnp provider delete checks ... +prohibit deletion of lnp providers if numbers are still linked to it +number+provider must be unique +fixed other panel lnp page validation checks +db constraints to stand concurrent inserts/updates +fixup all txn_do die() calls in panel to properly display the error +bulk upload checks by db constraints +lnp api testcase Change-Id: I872b19f50d96e6c39c7fd5728b2a16555a397236	9 years ago