This is actually several suggestions regarding the same annotation (ExoEntity). I've split them into separate commits to reflect the individual suggestions.

I don't mind if you implement this yourself without merging or implement only a part of these, but I figured I'd at least offer code.

IDE database integration for ExoEntity

59b036e adds a @Language annotation to ExoEntity#value annotation to enable IDE integration with the annotation.
This should simulate actual query usage of the given name. I noticed that names are always quoted in queries, so this is always quoted as well.

This enables:

• IDE database verification
• automatic refactoring by IDE database tools
• validity checking

ExoEntity implies @Serializable

In every single example usage of ExoEntity, as well as every example I find in the codebase, this annotation is always accompanied by @Serializable.

Add @MetaSerializable to ExoEntity

a1ee287 lets you omit @Serializable entirely when using that annotation.

So instead of

@Serializable
@ExoEntity("address")
data class AddressWithId(val ownerId: PersonId, val street: String, val zip: Int)

You can write simply

@ExoEntity("address")
data class AddressWithId(val ownerId: PersonId, val street: String, val zip: Int)

Extension: Make @ExoEntity a true alias of Serializable

As an extension of the previous, d267581 makes @Serializable completely optional in all cases:

So instead of

@Serializable
data class Address(val ownerId: Int, val street: String, val zip: Int)

You can write

@ExoEntity
data class Address(val ownerId: Int, val street: String, val zip: Int)

Extension: Add a docstring to @ExoEntity

134ebdb just adds a docstring to @ExoEntity, not sure what else to say.