I don’t think that Column’s lack of pertinence to some database types should be grounds for excluding it. It should be fine to standardize some API in Jakarta Data that will only apply to certain categories
of database types or patterns. Users of other database types to which it doesn’t apply can simply ignore and not use it.
That said, I’m also of the opinion (which might be in the minority) of preferring to see the Jakarta Persistence (JPA) specification continue to own and evolve the Entity model for relational databases, and
the Jakarta NoSQL specification continue to own and evolve the Entity model for the various NoSQL database types, with Jakarta Data repositories allowing either set of Entity annotations to be chosen based on whether the repository is for a relational versus
a NoSQL database type.
From:
data-dev <data-dev-bounces@xxxxxxxxxxx> on behalf of Graeme Rocher <graeme.rocher@xxxxxxxxx>
Date: Wednesday, October 5, 2022 at 1:24 PM
To: data developer discussions <data-dev@xxxxxxxxxxx>
Subject: [EXTERNAL] Re: [data-dev] @Column Annotation in Jakarta Data
Micronaut has @MappedProperty which can be interpreted in a database specific manner by the implementation but has no association with any particular database kind
(like @Column) On Wed, Oct 5, 2022 at 7: 14 PM Werner Keil <werner. keil@ gmx. net
This Message Is From an Untrusted Sender
|
You have not previously corresponded with this sender.
|
|
|
Micronaut has @MappedProperty which can be interpreted in a database specific manner by the implementation but has no association with any particular database kind (like @Column)
Mike,
While that certainly shouldn’t be considered the blueprint for everything, Spring Data (nor Micronaut Data) has no Column annotation.
And Jakarta NoSQL supports all relevant types of NoSQL database, @Column pretty much only makes sense for Column-based systems, therefore
I would not see that one as important.
Werner
I noticed on the Jakarta Data GitHub repository that there is no @Column
annotation defined yet.
I compared the corresponding @Column
annotations on the NoSQL
and Persistence
repositories and there are slight differences in the @Target annotation and there are additional
declared methods in the Persistence version of @Column for RDBMS.
Question: how do we proceed in creating a Jakarta Data version of the @Column
annotation to satisfy both the NoSQL and Persistence versions. I can, for example, start by creating a basic annotation and we can proceed from there.
--
Code,
Test, Write,
Cycle, Run,
Drink, Sleep
... Repeat
Lead Java Queue Editor, InfoQ
Laissez Les Bon Temps Rouler
he/him/his
_______________________________________________
data-dev mailing list
data-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org
--
|