![[ DeepNet IP Database ]](/images/ipdb-logo.png){kind=logo}
Custom Query (13 matches)
Results (10 - 12 of 13)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #24 | fixed | Block munging - "reserve space for growth" | ||
| Description |
In case of an allocation for a customer who may require more address space in the near future, and would like to keep that address space contiguous, allow a flag to be set on the original allocation (and the resulting free space blocks) that the free space immediately after the original allocation should be reserved to allow for this expansion. Needs to have a method to manually return this reserved space to the free pool in case of running low on available free blocks. |
|||
| #26 | fixed | Weed out ViaNet-isms | ||
| Description |
Trim out or generalize any remaining hardcoded ViaNet-specific bits. Most of these are docu-comments referring to ViaNet IP ranges. |
|||
| #34 | fixed | SQL cleanup - use DBI ? substitutions, move all SQL into IPDB.pm | ||
| Description |
Much of the SQL currently uses: $sth = $dbh->prepare("INSERT INTO table (cols) values ('$literal1','$literal2')");
$sth->execute;
instead of: $sth = $dbh->prepare("INSERT INTO table (cols) values (?,?)");
$sth->execute($literal1, $literal2);
Switching to CGI::Simple (#15) is exposing several places where this is problematic. This is also something of an SQL-injection security issue - using DBI's parameter replacement means that user data goes right into the table, instead of munging the SQL (deliberately or otherwise). |
|||
