Hi
Afair entityId is unique.
Regards
JB
Le mer. 26 mars 2025 à 20:27, Honah J. a écrit :
> Hi folks,
>
> I have a question about what constitutes a unique identifier for an entity
> in Polaris in the future.
>
> Right now, `lookupEntity` takes catalogId, entityId, and typeCode,
> following a r
Thanks for the clarification! Just to confirm — even though the entityId is
globally unique, we’ll still require catalogId + entityId at the
persistence API level to perform an entity lookup now and in the future,
correct?
On Wed, Mar 26, 2025 at 1:45 PM Dennis Huo wrote:
> Correct, the entityId
I'm OK with passing more through the interface. It's helpful in some use
cases. That said, we should clearly distinguish which parameters are
required and which are optional. Also, it's important to keep things
consistent across methods, such as between lookupEntity and lookupEntities.
>From what
This is more of an interface design question... I tend to think passing
more information down into the persistence layer is a good thing. So if
providing catalog ID, entity type, maybe even subtype, etc. can help the
persistence layer, we shouldn't be afraid to pass it down.
One other thing worth
I believe that entity ID by itself is meant to be a unique identifier.
On Wed, Mar 26, 2025 at 12:27 PM Honah J. wrote:
> Hi folks,
>
> I have a question about what constitutes a unique identifier for an entity
> in Polaris in the future.
>
> Right now, `lookupEntity` takes catalogId, entityId,
Correct, the entityId must be unique across all types.
On Wed, Mar 26, 2025 at 12:30 PM Eric Maynard
wrote:
> I believe that entity ID by itself is meant to be a unique identifier.
>
> On Wed, Mar 26, 2025 at 12:27 PM Honah J. wrote:
>
> > Hi folks,
> >
> > I have a question about what constitu
