TT#3994 Lnp and emergencymappings fixes after testing

Change-Id: I33a12ee198dd2d8270b2a10d6a71ef1227d40230
changes/46/8646/5
Irina Peshinskaya 10 years ago
parent c411f1b9c2
commit 4c27ee14ab

@ -43,6 +43,19 @@ sub query_params {
second => sub {},
},
},
{
param => 'reseller_id',
description => 'Filter for emergency mappings belonging to a specific reseller',
query => {
first => sub {
my $q = shift;
{ 'emergency_container.reseller_id' => $q };
},
second => sub {
return { join => 'emergency_container' };
},
},
},
{
param => 'code',
description => 'Filter for mappings with a specific code (wildcards possible)',

@ -93,10 +93,11 @@ sub update_item {
$self->error($c, HTTP_UNPROCESSABLE_ENTITY, "LNP carrier_id does not exist");
return;
}
if ($c->model('DB')->resultset('lnp_numbers')->search({
my $existing_number = $c->model('DB')->resultset('lnp_numbers')->search({
lnp_provider_id => $carrier->id,
number => $resource->{number}
},undef)->count > 0) {
},undef)->first;
if ($existing_number && $existing_number->id != $item->id) {
$c->log->error("LNP number '$$resource{number}' already defined for carrier_id '$$resource{lnp_provider_id}'");
$self->error($c, HTTP_UNPROCESSABLE_ENTITY, "lnp number already exists for lnp carrier");
return;

Loading…
Cancel
Save