TypeDB•2mo ago

Hi @krishnan

Hi @krishnan Thank you for the help. I am revisiting your sample schema. I understand the first part, and I rewrote it to the below working query.

define attribute ipo-date, value datetime;
relation attributed-ownership @abstract, relates source;
entity data-source plays attributed-ownership:source;
relation attributed-ipo-date sub attributed-ownership, owns ipo-date;

define attribute ipo-date, value datetime;
relation attributed-ownership @abstract, relates source;
entity data-source plays attributed-ownership:source;
relation attributed-ipo-date sub attributed-ownership, owns ipo-date;

it works pretty well. So with this, for any attribute XXX, I just need to attach a relation called attributed-XXX and then I can define the attribution. Very neat. I am also wondering, should attributed-ipo-date uses relate for ipo-date, so that when ipo-date attribute got deleted/changed, this relation attributed-ipo-date can be deleted as well? I want the attribution go away with the referenced ipo-date attribute and referenced entity instance go away. ============ But I don't understand the second example. I kept getting error with the second approach in your comment.

define AttributedOwnership owns AttributedValue;
attribute AttributedDateValue  @abstract, sub AttributedValue , value date;

relation AttributedDateOwnership @abstract, sub AttributedOwnership, owns AttributedDateValue as value;
relation AttributedIPODate sub AttributedDateOwnership;

define AttributedOwnership owns AttributedValue;
attribute AttributedDateValue  @abstract, sub AttributedValue , value date;

relation AttributedDateOwnership @abstract, sub AttributedOwnership, owns AttributedDateValue as value;
relation AttributedIPODate sub AttributedDateOwnership;

Can I have a full, working implementation of the second approach? I am not sure if I understand this.

15 Replies

kenho811OP•2mo ago

A related question is, for the relation attributed-ipo-date, I want it to be auto deleted when say, the owned ipo-date got deleted or replaced. Also, if it is an entity actually owning ipo-date, say it is a company entity owning ipo-date. I observe that, if I delete the company entity instance, the attributed-ipo-date relation seems to remain. ================== They are a number of items I want attribution for - an entity' attribute (e.g. a company's ipo-date comes from a news article) - a relation between entities (e.g. the contractual relation between company A and company B comes from a news article) How can I use the construct you suggested to achieve the attribution?

krishnan•2mo ago

Adapted this to commit:

define 
attribute AttributedValue @abstract;
relation AttributedOwnership @abstract, relates Owner, owns AttributedValue;
attribute AttributedDateValue, sub AttributedValue , value date;

relation AttributedDateOwnership @abstract, sub AttributedOwnership, owns AttributedDateValue;
relation AttributedIPODate sub AttributedDateOwnership;

define 
attribute AttributedValue @abstract;
relation AttributedOwnership @abstract, relates Owner, owns AttributedValue;
attribute AttributedDateValue, sub AttributedValue , value date;

relation AttributedDateOwnership @abstract, sub AttributedOwnership, owns AttributedDateValue;
relation AttributedIPODate sub AttributedDateOwnership;

define entity company, plays AttributedOwnership:Owner;

insert 
$company isa company;
$rel isa AttributedIPODate(Owner:$company), has AttributedDateValue 2025-07-20;

insert 
$company isa company;
$rel isa AttributedIPODate(Owner:$company), has AttributedDateValue 2025-07-20;

Now deleting the company turns any AttributedOwnerships it plays the owner role in to have 0 role-players and get cleaned up. You could tighten AttributedOwnership:Owner to be @card(1) as well.

a relation between entities

This will be harder to achieve, but we were meant to introduce an @cascade at some point to allow cleaning up relations if any role fell below cardinality requirements. For now, you may have to garbage collect Oh hold on, I've fallen out of context here. I don't have the attribution do I? In that case you'll need to run a GC query even for ownerships.

kenho811OP•2mo ago

@krishnan Following up on this, so @cascade is not yet implemented? https://typedb.com/docs/typeql/annotations/cascade

krishnan•2mo ago

I don't think it is implemented. It's non-trivial since it does cascade (potentially deleting a huge number of relations) but might not be tooooo hard to implement either

kenho811OP•2mo ago

Understood. btw, what's the current behaviour when a relation relates multiple entities, and one of the entities got deleted? For relation attribution, I wonder if I can do this

define relation attributed-relation @abstract, relates source

define relation has-agreement sub attributed-relation, relates company @card(2..), owns start-date

define relation attributed-relation @abstract, relates source

define relation has-agreement sub attributed-relation, relates company @card(2..), owns start-date

say now I have

insert has-agreement (company:$companyA, company:$companyB, source:$source), has start-date 2025-01-01

insert has-agreement (company:$companyA, company:$companyB, source:$source), has start-date 2025-01-01

if now I delete $companyA, does the has-agreenent relation instance still exist?

krishnan•2mo ago

Yes, it should still exist. Oh wait, You'll get a cardinality violation error and the commit will fail

kenho811OP•2mo ago

Oh. I see. because the cardinality constrains it to at least 2 instances. OK what if I delete $source ? does the relation instance has-agreement still exist?

krishnan•2mo ago

It should.

kenho811OP•2mo ago

How do I achieve this? Say I make the source role mandatory. When I delete a source instance, I want all relations with the source instance to be deleted I dont want anything unattributed to any source. If I deem a source to be bad, I want to get rid of all the data associated with said source

krishnan•2mo ago

Can you do it manually for now?

kenho811OP•2mo ago

Can you give me the manual typeQL?

krishnan•2mo ago

match 
  $source isa source, has ...;
  $relation links ($source);
delete 
  $relation;
delete 
  $source;

match 
  $source isa source, has ...;
  $relation links ($source);
delete 
  $relation;
delete 
  $source;

kenho811OP•2mo ago

Oh. that makes sense. Thanks! that's actually easy to read!

krishnan•2mo ago

It is nice isn't it?

kenho811OP•2mo ago

Thanks for helping me out with designing this attribution-enabled graph. Spent so many days figuring out stuff. My takeaway: - entity-owns-attribute attribution: A relation which relates an entity, relates a source and owns the attribute - relation-attribution: In existing relation, add a relates source role. then done

Gaming

Programming

Hi @krishnan

Did you find this page helpful?