Re: [data-dev] Jakarta Data

[Otavio Santana <otaviopolianasantana@xxxxxxxxx>]

Debugging and Understanding

Jakarta Data itself does not define specific tools or mechanisms for debugging. The approach to debugging may vary depending on the database and the Jakarta Data provider being used. For example:

• Hibernate (for SQL databases) provides various debugging tools and logging properties, such as hibernate.show_sql and hibernate.format_sql, which helps track executed queries.
• Eclipse JNoSQL (for NoSQL databases) has its debugging strategies depending on the database driver and configuration.

Since Jakarta Data abstracts database interactions, the debugging experience depends on the underlying provider. Developers should refer to their specific Jakarta Data implementation and database tooling for effective debugging strategies.

On Fri, Feb 21, 2025 at 9:16 AM Gabriel Cunha via data-dev <data-dev@xxxxxxxxxxx> wrote:

Kyle, thanks for your inputs!

Actually, this point is my weakest link among the 4 others. What I mean by that is that using Jakarta Data makes your persistence layer easier to debug and then understand what happens behind the scenes when compared to other tools.

I would be willing to replace any of these topics, including this one, for some other Jakarta Data detail that makes it more appealing to the audience. But those 5 are the best I could find so far.

Em qui., 20 de fev. de 2025 às 12:33, Kyle Aure <kylejaure@xxxxxxxxx> escreveu:

Hi Gabriel,

I'm glad to hear you are planning a talk about Jakarta Data.

Your list looks good, but I'm wonder what specifically you are planning to talk about for

3 - Debbuging and understanding

I think if I were reading an abstract for a talk that used that as a topic I would expect the framework to provide

some novel debugging tool and/or documentation.  The Jakarta Data specification does specify any more than 

when providers must throw errors and what type of errors.

Are these things provided by quarkus or am I misinterpreting the topic?

Thank you,

Kyle Jon Aure

On Wed, Feb 19, 2025 at 11:11 PM hantsy bai via data-dev <data-dev@xxxxxxxxxxx> wrote:

Ok, thanks for the clarification.

---

Regards,

Hantsy Bai

Self-employed consultant, fullstack developer, agile coach, freelancer/remote worker

GitHub: https://github.com/hantsy

Twitter: https://twitter.com/@hantsy

Medium: https://medium.com/@hantsy

On Thu, Feb 20, 2025 at 1:09 PM Gabriel Cunha <cunha.gabriel919@xxxxxxxxx> wrote:

I dont mean entities relationship, I mean how many repositories you have for different entities.

One repo for one entity, one repo for multiple entitie, without being forced to extend some kind of CrudRepository that forces to have an entire repository all about a single entity.

That was confusing, my bad! And thanks for answering!

Em qui., 20 de fev. de 2025 às 02:04, hantsy bai <hantsy@xxxxxxxxx> escreveu:

Jakarta Data does not help you handle entity relations; the Jakarta Persistence cascade options do not work in Jakarta Data.

---

Regards,

Hantsy Bai

Self-employed consultant, fullstack developer, agile coach, freelancer/remote worker

GitHub: https://github.com/hantsy

Twitter: https://twitter.com/@hantsy

Medium: https://medium.com/@hantsy

On Thu, Feb 20, 2025 at 11:31 AM Gabriel Cunha via data-dev <data-dev@xxxxxxxxxxx> wrote:

Hey, guys!

I'm preparing a talk about Jakarta Data. The main goal with the talk is to rethink Data Repositories using Jakarta Data and Quarkus.

I want to cover up to 5 topics on how Jakarta Data helps us to implement the persistence layer in a different way. Here are a few topics I wrote down while reading and watching other presentations:

1 - Type safety
2 - Repository/Entity relationship: One to one, one to many, many to many
3 - Debbuging and understanding
4 - Simpler queries
5 - Flexibility and productivity

Any thoughts on these 5, specifically if they are accurate according to Jakarta Data goals or if any of these could be replaced by a different topic?

If there's a different mailing list or forum where I should send this question, just let me know!

Thanks in advance!

_______________________________________________
data-dev mailing list
data-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org

_______________________________________________
data-dev mailing list
data-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org

_______________________________________________
data-dev mailing list
data-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org

--

Thanks a lot,

Twitter | Linkedin | Youtube