On 07/09/12 17:01, Francesco Panico wrote:
We report the experience on last official SDB release.
We do not find a change log on 1.3.5 so we do not know if the bug has been
fixed. We have to test it.
Great - I believe that the issue you encountered is fixed. The
migration from SourceForge to Apache makes it a little harder to track
although I believe that the entire history was imported when we imported
into Apache SVN.
I'd certainly hope so ... the ingest took quite a long time during which
ASF SVN was read only (planned - 1 hour - actually 4+ hours - oops!)
because of the long history.
Andy
Regards
Francesco
2012/9/6 Andy Seaborne <[email protected]>
On 06/09/12 13:21, Francesco Panico wrote:
2-Oracle DB support:
SDB support oracle DB 10g.
We tested it and we find a bug.
SDB translates SPARQ to SQL query properly but the outcome query contains
some sql command that Oracle 10g does no supports.
For example the outcome query contains "Limit" (it work properly using
mysql DB). In Oracle DB you should use "rownum" instead.
SDB Version (date of download, output of "sdbprint --version"): 1.3.4
Hi there,
Thanks for the reports for MySQL and Oracle 10g.
Was that "1.3.4" a mistake?
The proposed release candidate is 1.3.5-SNAPSHOT
Andy
