Hi Robert, :) I suppose this is where it gets confusing
I am thinking of structuring it with BT 2x2 max depth and length, i.e "a" -> /dict/a (virtual=false) "axe" -> /dict/ax/axe "apache" -> /dict/ap/ac/apache Another question arises with this is how do we back reference in to foreign representation. i.e where lets say axe = hache, maybe use of mix:referencable and reference to it "apache" -> /dict/ap/ac/apache/@references['xxxxxxx-xxxxxx'] or when you have a word that has same spelling in multiple languages Eren On 2 May 2018 at 14:28, Robert Munteanu <[email protected]> wrote: > Hi Eren, > > On Mon, 2018-04-30 at 20:36 +0300, Eren Erdemli wrote: > > Greetings, > > > > Might be a naive question, > > > > I have a multi dictionary app built on mysql which is around 15 years > > old. > > and have around 500GB of data > > > > I wonder if using oak mongomk is suitable option for porting this > > app, > > Maybe :-) > > How do you see the data structured in Oak? I guess the first idea would > be to somehow avoid having a large number (>10k) of orderable child > nodes directly below a single node. > > Robert >
