annotate tests/0033/run-test.sh @ 584:e3790284fd4a

Merged through librdf storage hooks and apache2 module.

Squashed commit of the following:

commit a6cfca8f04036e12e7d7fcd55c47224e802582f0
Author: Michael Jewell <mjewell@harrison.(none)>
Date:   Fri Jul 31 15:23:32 2009 +0100

    Removed leftover bits and bobs.

commit f1f0dd074d0767de3e24ba636779fd8701d73d9e
Author: Michael Jewell <mjewell@harrison.(none)>
Date:   Fri Jul 31 15:07:20 2009 +0100

    Simple test of database creation via librdf.

commit 90e6350538e004d8785137e5ff2ac878c22a5d42
Author: Michael Jewell <mjewell@harrison.(none)>
Date:   Fri Jul 31 15:05:10 2009 +0100

    Added the apache2 module which will hook into the librdf storage module

commit c75bf53763b7078c83ae97fcf247da2576baa79a
Author: Michael Jewell <mjewell@harrison.(none)>
Date:   Fri Jul 31 15:04:53 2009 +0100

    Added sparql librdf source - requires the librdf sources to compile.

commit 0646f0190112a73ddb2533537e2cc9832c066b52
Author: Michael Jewell <mjewell@harrison.(none)>
Date:   Mon Jul 27 12:12:26 2009 +0100

    Adding execution to mod_audiodb

commit 8f83f27ba4d917278bca0c7cb665d930e28c86df
Author: Michael Jewell <mjewell@harrison.(none)>
Date:   Wed Jul 22 12:15:57 2009 +0100

    Some initial returns for the sparql handler.

commit dc639aed11943a5b0c379eb47cf293f76908b1b7
Author: Michael Jewell <mjewell@harrison.(none)>
Date:   Wed Jul 22 12:06:20 2009 +0100

    Added a little setup.sh script to do libtoolize/autoconf etc.

commit 3a679da499db647fc82cf2797daeb5cc44ed7655
Author: Michael Jewell <mjewell@harrison.(none)>
Date:   Wed Jul 22 12:03:42 2009 +0100

    Adding initial bits for apache mod

#! /bin/bash

. ../test-utils.sh

if [ -f testdb ]; then rm -f testdb; fi

${AUDIODB} -d testdb -N

intstring 2 > testfeature01
floatstring 0 1 >> testfeature01
intstring 2 > testfeature10
floatstring 1 0 >> testfeature10

${AUDIODB} -d testdb -I -f testfeature01
${AUDIODB} -d testdb -I -f testfeature10

# sequence queries require L2NORM
${AUDIODB} -d testdb -L

echo "query point (0.0,0.5)"
intstring 2 > testquery
floatstring 0 0.5 >> testquery

${AUDIODB} -d testdb -Q sequence -l 1 -f testquery -R 5 > testoutput
echo testfeature01 1 > test-expected-output
echo testfeature10 1 >> test-expected-output
cmp testoutput test-expected-output
${AUDIODB} -d testdb -Q sequence -l 1 -f testquery -K /dev/null -R 5 > testoutput
cat /dev/null > test-expected-output
cmp testoutput test-expected-output

echo testfeature01 > testkl.txt
${AUDIODB} -d testdb -Q sequence -l 1 -f testquery -K testkl.txt -R 5 > testoutput
echo testfeature01 1 > test-expected-output
cmp testoutput test-expected-output
echo testfeature10 > testkl.txt
${AUDIODB} -d testdb -Q sequence -l 1 -f testquery -K testkl.txt -R 5 > testoutput
echo testfeature10 1 > test-expected-output
cmp testoutput test-expected-output

echo testfeature10 > testkl.txt
${AUDIODB} -d testdb -Q sequence -l 1 -f testquery -K testkl.txt -r 1 -R 5 > testoutput
echo testfeature10 1 > test-expected-output
cmp testoutput test-expected-output

# NB: one might be tempted to insert a test here for having both keys
# in the keylist, but in non-database order, and then checking that
# the result list is also in that non-database order.  I think that
# would be misguided, as the efficient way of dealing with such a
# keylist is to advance as-sequentially-as-possible through the
# database; it just so happens that our current implementation is not
# so smart.

echo "query point (0.5,0.0)"
intstring 2 > testquery
floatstring 0.5 0 >> testquery

${AUDIODB} -d testdb -Q sequence -l 1 -f testquery -R 5 > testoutput
echo testfeature01 1 > test-expected-output
echo testfeature10 1 >> test-expected-output
cmp testoutput test-expected-output

echo testfeature10 > testkl.txt
${AUDIODB} -d testdb -Q sequence -l 1 -f testquery -K testkl.txt -r 1 -R 5 > testoutput
echo testfeature10 1 > test-expected-output
cmp testoutput test-expected-output

exit 104