I have come across this in the documentation: And it is exactly what is
happening. Any suggestion on how to avoid embedding in the property and
instead have a separate record.
Embedded relationships
Embedded records, instead, are contained inside the record that embeds
them. It's a kind of relationship stronger than the
[#Referenced_relationships reference]. The embedded record will not have a
own [Concepts#RecordID RecordID] since it can't be directly referenced by
other records. It's only accessible via the container record. If the
container record is deleted, then the embedded record will be deleted too.
Example:
address
Record A <>----------> Record B
CLASS=Account CLASS=Address
RID=5:23 NO RID!
*Record A* will contain the entire *Record B* in the property called
"address". *Record B* can be reached only by traversing the container
record.
On Sunday, January 25, 2015 at 10:53:20 PM UTC+4, Kareem Jabr wrote:
>
> Hi,
>
> I have updated the database to 2.0 and I was using 1.7.10 before. Suppose
> I have the below scenario:
>
> Account -> Person
> And
> Account -> List<Event> eventsList
>
> When I save the account populated with a person and many events. Events
> are saved but the person object is not!!! And person table never gets any
> records. I noticed this only in case of single nested object and saving the
> parent.
>
>
> Thanks,
> Kareem
>
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
