This is the first draft of creating layer3domains and
ipblocks/containers.
This allows some testing with different things, like list building for
complex container output, but also how containers should behave.
Containers are subnets in vairous ranges. But only when a subnet is
assigned a pool, it is truly a subnet. When it is not assigned to a
pool, it is considered a container.
This serves the purpose of grouping or blocking containers for different
purposes, so we need to keep that up.
When extra fields are fetched from the attributes column it must be
specified from which table that should be. If not done and another table
also has an attribute column, it will end in an error.
This modifies the zone list command in such a way, that a query result
could be directly returned to the response.
With a bit of work, large query results could be rendered with a
streaming json renderer to the output.
This type represents a list of fields someone might want to have
returned.
This can be used together with the query library to build select
statements that return the exact data the user might need or want.
This way we may be able to avoid selecting data one might not need at
the end and therefore provide better performance.
This is a small library to build queries and put the result into the
world.
Currently it supports building the select clause and converting rows
into a list of maps, so that it can be returned as a list.
This package will contain all the parameter types that need parsing from
the outside world into internal types.
Each type is required to implement its own UnmarshalJSON. At this point
it should also make the checks, if the incoming data is valid input, but
is not required to check against the database.
These helpers enable the parameter parsing into method specific structs.
As the parameter list is an array, the order of arguments is important.
Sadly type checks can be done at runtime, because all parameters are
converted to a list of interface{}. So if there is an error, it will
only result in an error at runtime, so be careful.
This adds the transaction handling to the connection and context
handling.
It will raise an error and inform the client if anything is going wrong
with the transaction.
Gibheer