Well you have several ways. Do you want to do it with JAVA oder the ETL
plugin?
In any case I think it should be
Vertices: Author, Book
Edge: WROTE
WDYT?
Am Montag, 20. Oktober 2014 10:51:03 UTC+2 schrieb Bojan Vukotić:
>
> Hi guys!
>
> The whole discussion here is how to create edges from one table to
> another, but what to do if we have more complex cases where we have
> connected 2 (or even more) tables? Example, n:n relation: book and authors,
> book can have one or more authors and author can work on one or more books.
>
> Tables:
>
> Book {
> book_id
> book_name,
> ....
> }
>
> Author {
> author_id,
> author_name,
> ......
> }
>
>
> Author_on_Book {
> ab_id,
> book_id,
> author_id,
> description // describes what this author did on this book
> }
>
> How to migrate this case? Should "Author_on_Book" be migrated as a vertex
> or edge? How to write scripts in this case? (in real life we could have
> even more foreign keys in "Author_on_Book" table )
>
>
>
--
---
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.
