DB Client examples

[Tomas-Kraus]

DB Model:

• Types (id, name) -- Pokemon type table
• Pokemons (id, name, id_type) -- Pokemon entity table with Types(id) reference

Use-cases:

• List all Pokemons (without types)
• Get pokemon by ID
• Get pokemon by name
• Create pokemon
• Update pokemon
• Delete pokemon by ID

Readme

• https://github.com/Tomas-Kraus/helidon/tree/master/examples/dbclient/pokemons

[m0mus]

I don't like many-to-many. For a simple demo we should stick with one-to-many relationship.

[tomas-langer]

The current DB example should be left to demonstrate similiarity when using JDBC and mongo.
Also create a separate example for JDBC and for Mongo that will show more than one table that can be used by customers to "bootstrap" their microservice.

[Tomas-Kraus]

@m0mus Bad news is, that I've already done 90% of the demo and it works for both Mongo and JDBC. But I can create another more simple sample with following 1:N schema:

• Trainer (id, name) -- pokemon trainer
• Pokemon (id, name, id_trainer) -- pokemon caucht by trainer

And we can make following services:

• add trainer [CREATE]
• rename trainer [UPDATE]
• delete trainer (and all his pokemons) [DELETE]
• catch pokemon (by trainer) [CREATE]
• rename poemon [UPDATE]
• release pokemon (by trainer) [DELETE]
• list all trainers without pokemons [READ]
• list all pokemons with trainer who owns them [READ with join]
• get pokemon [READ]
• get trainer with pokemons list [complex READ]

[m0mus]

@Tomas-Kraus I can only repeat that many-to-many sample is too complex for a simple demo. A new sample you are talking about technically contains 3 tables:

• trainers
• pokemons
• trainer_pokemon

where trainer_pokemon is many-to-many between 'trainersandpokemons`. So, it's the same use case.

[Tomas-Kraus]

JDBC Sample was rewritten to match @m0mus requirements. MongoDB is still in TODO list.

[Tomas-Kraus]

Modified README content is here: https://github.com/Tomas-Kraus/helidon/tree/master/examples/dbclient/pokemons

[m0mus]

@Tomas-Kraus If review comments are addressed please resolve those conversations. It's difficult to review.