It's https://issues.apache.org/jira/browse/JENA-27
Hopefully someone can get round to testing it against PostgreSQL and the
other databases.
On 10/02/11 21:22, Mike Spreitzer wrote:
OK, based on your remarks it may be easy for me to figure out how to fix
the syntax problem. BTW, DB2 Express is free to everyone.
But admin time for ~8 database engine is not :-)
Andy
I am more concerned by the Null bridge complaint. I wonder what's going
wrong there. I do not know anything about the code, but wonder whether
that problem is specific to DB2. I Googled for `sdb "null bridge"` and
found that someone submitted a fix in November for a Null bridge problem (
http://tech.groups.yahoo.com/group/jena-dev/message/45856). How can I
confirm that I already have that fix? I downloaded SDB-1.3.3, which is
dated Dec 22, from http://sourceforge.net/projects/jena/files/SDB/
Has anybody run the full test suite that I did, on SDB of any recent
vintage?
Thanks,
Mike Spreitzer
SMTP: [email protected], Lotus Notes: Mike Spreitzer/Watson/IBM
Office phone: +1-914-784-6424 (IBM T/L 863-)
AOL Instant Messaging: M1k3Sprtzr
From: Andy Seaborne<[email protected]>
To: [email protected]
Date: 02/10/2011 03:21 PM
Subject: Re: Problems with SBD tests
On 10/02/11 20:08, Mike Spreitzer wrote:
No, not a complete solution. The Slice 3 test uses OFFSET without
LIMIT.
That is not valid syntax for MySQL, and it is not accepted by DB2 with
MySQL compatibility turned on.
Also, the Slice 1 test now fails in a new way; following is an excerpt
from a typescript of running with -v --log=all. What does this "Null
bridge" complaint mean?
INFO [main] (SDBConnection.java:338) - execQuery
SELECT R_1.lex AS V_1_lex, R_1.datatype AS V_1_datatype, R_1.lang AS
V_1_lang, R_1.type AS V_1_type, R_1.lex AS V_2_lex, R_1.datatype AS
V_2_datatype, R_1.lang AS V_2_lang, R_1.type AS V_2_type
FROM
Triples AS T_1
LEFT OUTER JOIN
Nodes AS R_1
ON ( T_1.p = R_1.hash )
LIMIT 3
ERROR [main] (SDB_QC.java:64) - Null bridge
When was the last time anyone used SDB? Does it actually work with
anything?
Mike - sorry your having probelms. DB2 support was a user contribution.
In a previous employment, I had access to a DB2 express installation
for testing. I'm afraid that we don't have access to all the databases
these days and so rely on the RC cycle for some setups.
The class GenerateSQLDB2 is the DB2 specific adapter which creates the
writer for Db2 specific syntax - that's GeneratorVisitorDB2.
Syntax is written by overrideable method
genLimitOffset(SqlSelectBlock). If you can submit a patch for what
should be done for DB2, we can include in the next release.
Less ideally, this can be turned off
SDBRequest.compile sets up the per-store type configuration. This can
turn off limit/offset generation in SQL.
Andy
Thanks,
Mike Spreitzer
SMTP: [email protected], Lotus Notes: Mike Spreitzer/Watson/IBM
Office phone: +1-914-784-6424 (IBM T/L 863-)
AOL Instant Messaging: M1k3Sprtzr
From: Mike Spreitzer/Watson/IBM@IBMUS
To: [email protected]
Date: 02/10/2011 02:32 PM
Subject: Re: sdbtest uses "LIMIT"
FYI, I found a solution. Install Fix Pack 2 or later (I am using 3a),
it
introduces a compatibility option that makes it accept LIMIT and OFFSET.
Regards,
Mike Spreitzer
SMTP: [email protected], Lotus Notes: Mike Spreitzer/Watson/IBM
Office phone: +1-914-784-6424 (IBM T/L 863-)
AOL Instant Messaging: M1k3Sprtzr
