World: r3wp

It's the problem, I think Terry can't decide :-)

Ok, I give it to you...

Tweety
 "age" "75"
Steeve
 "isa" "Rebol"
Steeve
 "age" "unknown"

I have a system working now that's fast enough.. but I'm a speed 
junkie.. there must be a BEST way (not better... BEST)

First i add the triple in the triples store (a simple block)

The, I recovers its index from the block (actually it's the last 
one)

And i use this index as the value for the 3 indexes, and i create 
the keys+value
Tweety
: index
Isa
: index
Canary
: index

that's all...

yeah, but ...

Perhaps the explanations are not clear, but it's pretty clear in 
my head ;-)

>> ie: ["Tweety" "isa" "canary"]
== ["Tweety" "isa" "canary"]
>> index? find ie "Tweety"
== 1

Great.. now what

( only in Rebol does ie: actually mean ie: )

(added In index1) "Tweety"= index
(added In index2) "Isa"= index
(added In index3) "Canary"= index

(added In index1) "Tweety"= index
(added In index2) "Isa"= index
(added In index3) "Canary"= index

so now i want to query, say , everything that is "age" "75" (like 
above)

by doing, index2/"age" you'll get all the triple having the verb 
"age"

with index3/"75", you'll get those with 75 as the target

then intersect the 2 blocks

I just think you don't get it, but I know my explanation sucks, sorry.

i get it.

Ron Everett presented  a database that did much of what you want 
at DevCon2007. The live discussion is here:

   http://www.rebol.org/aga-display-posts.r?offset=0&post=r3wp500x1919
The video of the presentation may be on qtask.

yeah, associative stuff :-)

Senteces from Lazysoft was another product of such kind ...

i remember that

http://www.rebol.net/cgi-bin/r3blog.r?view=0161

And my comment...

it's remember me the IDE Plex(obsydian) in the nineties. it used 
widely the concept of triples (tuples) to modelize applications and 
databases.

hmm, i thought i got it. :( now I'm lost in block hell

nope.. i got it again :)

Should have listened to my mother and became a lawyer.

why :-)

Shouldn't Intersect take an block of blocks?

ie: intersect [ blk1 blk2 blk3.. ]

Works great Steeve. I haven't benchmarked it yet, but given the whole 
thing can sit in hashes or maps! , i would say the performance should 
be spectacular

Terry, I think INTERSECT is fine the way it is, and it's easy to 
wrap if you want.

    fold: func [
        series [series!]
        fn     [any-function!]
        /local value
    ][
        value: pick series 1
        foreach item next series [value: fn value item]
    ]

    intersect-all: func [
        series [block!] "A block of series values to intersect"
    ][
        fold series :intersect
    ]

I knew someone would comback with a function.. might as well have 
been you Gregg.
I like PHP's array_merge()

steeve, REBOL doesn't support path with strings, and furthermore, 
it would only return the first index, if you used it within a paren.


so I'd really like you to give a small snippet of code with your 
idea, I am curious about your method... cause I don't see *how* what 
you say works.

I would use map! (or hash!) as indexes and a key would contain one 
or several triples (inside a block)
verb/"age": [ index indexn ...]

Max, Steeve proposed the datastructure so, that the above feach operations 
become elementary ("instantaneous").

Yeah !!! :)

Here's what I did..

ie: [["Steeve" "isa" "person"]["Steeve" "age" "42"]["Tweety" "isa" 
"Canary"]["Tweety" "age" "75"]["Chirp" "isa" "Canary"]]
i1: ["Steeve" [1 2] "Tweety" [3 4] "Chirp" [5]]
i2: ["isa" [1 3 5] "age" [2 4]]
i3: ["person" [1] "42" [2] "Canary" [3 5]]


rocket: func [it][
    st: now/precise

	while[it > 0][
		s: i1/("Steeve")
		p: i2/("isa")

		res1: intersect s p
		it: it - 1
	]
	prin join " -> " difference now/precise st
]

Yeah !!! You got it :)

and i1,i2,i3 should be of type hash! or map!

This finds all "Steve isa... "

If i wanted to find all "Canaries".. 

p: i2/("isa")
v: i3/("Canary")

result intersect p v

yeah.. im just building some benchmarks with real data now

my rebol is so rusty.. how do i turn 

["2c3cukne98" "femaleend" "E1016 Camlok" "2c3cukne98" "isa" "cable" 
"2c3cukne98" "uid" "8558"... ]

into 

[["2c3cukne98" "femaleend" "E1016 Camlok"][ "2c3cukne98" "isa" "cable" 
]["2c3cukne98" "uid" "8558"]...

remold make-block reduce enlarge.. or somethin.. ?

map-each

To make it practical for other operations too, the triple store should 
be defined so, that:


1) every triple is stored as a fourtuple, the additional field being 
a unique triple ID
2) create the main index using the triple ID, 

3) create three field indices searchable by by the field contents, 
and "inside" also by the main ID


This way, the triple storage will be moderately fast for triple removal 
as well

For R2, I wrote a function called Stagger for that:
Stagger: func [L I /local][
    forall L [
        L/1: copy/part L I 
        remove/part next L (I - 1)
    ] 
    return L
]

>> Stagger ["2c3cukne98" "femaleend" "E1016 Camlok" "2c3cukne98" 
"isa" "cable" "2c3cukne98" "uid" "8558"] 3

== [["2c3cukne98" "femaleend" "E1016 Camlok"] ["2c3cukne98" "isa" 
"cable"] ["2c3cukne98" "uid" "8558"]]