diff --git a/docs/index.html b/docs/index.html index 2cb8d1e..536a7ee 100644 --- a/docs/index.html +++ b/docs/index.html @@ -114,6 +114,32 @@ dbadmin.modelsPackage=your.models.package,your.second.models.package

This will autoconfigure the various Spring Boot Database Admin components when your application starts.

If everything is setup correctly, you will see Spring Boot Database Admin confirming it in the log messages that appear when you start your application. Keep in mind that if you specify the wrong models package, it will still work but provide you an empty interface. To check, visit http://localhost:8080/admin.

+ +

2.3 Supported features

+

+

2.3.1 Supported JPA annotations

+ +

The behaviour you specify with these annotations should be applied automatically by Spring Boot Database Admin as well. Keep in mind that using non-supported annotations will not necessarily result in an error, as they are simply ignored. Depending on what the annotation actually does, this could be just fine or result in an error if it interferes with something that Spring Boot Database Admin relies on.

+ +

2.3.2 Supported field types

+ + +

Unsupported field types are handled as gracefully as possible, meaning that when such a field is detected the application will run anyway but this field will never be displayed in the web interface. This also means that it will not be possible to enter the value for this field when editing or creating, leaving it as the default NULL value. If the field is not nullable, you will thus not be able to create items.

+

To check if your code contains unsupported fields:

+ +

3. Customization

There are two ways to customize the appearance and behaviour of Spring Boot Database Admin: