The database constraints will catch the same error
(and raise an IntegrityError).

Having some validation at the model level allows to display nicer error
messages.
We use CSEntryError exception and not ValidationError so that it can be
used both by the API and views.

Allow to use the same CSEntryError exceptions used for validation
in the API and admin views.

Trying to insert an invalid IP or network address raises an exception.
This is due to the unique validator from flask-admin that queries the
database.

The unique validator is automatically added for columns with
unique=True. The only way to disable it is to monkey patch the Unique
class.
This allows the field validator to catch invalid format.

IntegrityError are already catched anyway.

- replace TextAreaField by StringField for several Text columns
- add filter to replace empty string by None on optional Text and INET
  fields

Don't override the Admin view __init__ method for consistency.
Avoid having to import models in admin/views.py

CIText is displayed as a TextAreaField by flask-admin.
Override it to use StringField.

- Allow to pass several mandatory fields in create_generic_model
- Add tests

- A network defines an available range of IP addresses
- A host defines an IP address and name
- A host is always linked to a network
- A mac address is always linked to an item (physical equipment)
- A mac address can be linked to one host (IP)
- An item can have several mac addresses

Text is as efficient in Postgres and is recommended over varchar.
It avoids having to put an arbitrary max length to strings.

CSE makes it clearer that it's linked to CSEntry

This reverts commit 8d6acd19.

See https://issues.jenkins-ci.org/browse/JENKINS-46736

Bug in bitbucket team project?

Client moved to its own repository (ics-inventory-client)

Add button to return to main index

ics_id, serial_number, manufacturer_id and model_id should not change.
Repeating them in the history table takes space for nothing.

We are only interested in tracking the status, location and parent.

- catch IntegrityError on patch
- disable autoflush (IntegrityError was raised before commit due to
autoflush)

Pass ?qrcode=true as query string

Fix default button issue on login page

- use same postgres container for dev and test
  (create 2 different databases)
- use docker-compose.override.yml to avoid duplication
- ignore more files not needed in the docker image

By default docker-compose reads both docker-compose.yml and
docker-compose.override.yml.
In docker-compose.override.yml we mount the current directory as
a volume for development.

To test the image we only use docker-compose.yml:
- don't force port 5432 to the outside world to avoid conflict
- do not mount the current directory

- change label (jenkins-slave should have docker-compose installed)
- only push when the current commit is a tag