  Learning Center
  Documentation
  Updates
    • Info
  FAQ

The following patches are now available. See the Franz Patch page for more information on downloading and installing patches.

There are currently 27 patches (27 unique).

agraph patch
Date posted:	Wed Sep 5 10:33:16 PDT 2007
Patch name:	update/agraph/2.2/pfo016.001
Description:	Corrects a reasoner bug that manifest when rdfs:subClassOf (or rdfs:subPropertyOf) hierarchies became sufficiently complex. In these situations, the reasoner would lose track of much of the hierarchy and produce incorrect results.
Impact:	recommended

agraph patch
Date posted:	Thu Aug 30 12:44:15 PDT 2007
Patch name:	update/agraph/2.2/pfo015.001
Description:	Fixes an incorrect results format (SPARQL Turtle) for remote queries. This patch also allows additional arguments to run-sparql-remote to be propagated to AllegroServe.
Impact:	recommended

agraph patch
Date posted:	Thu Aug 30 12:44:15 PDT 2007
Patch name:	update/agraph/2.2/pfo014.001
Description:	AllegroGraph Lisp CLient API calls with encoded literal argument was signalling an error in the server. This patch corrects the problem.
Impact:	recommended

agraph patch
Date posted:	Fri Aug 17 12:27:19 PDT 2007
Patch name:	update/agraph/2.1/pfo011.001
Description:	Corrects the reasoner's handling of rdf:type queries when neither the subject nor the object is specified. The reasoner was mistakenly caching the same value for each subject instead of a different value for each subject. This caused it to return duplicate results instead of the correct ones.
Impact:	recommended

agraph patch
Date posted:	Wed Aug 15 15:08:34 PDT 2007
Patch name:	update/agraph-2.1/pfo010.001
Description:	Adds logic to handle transitive reasoning for subClassOf and subPropertyOf and alters the reasoner code to collect all results instead of just the first.
Impact:	recommended

agraph patch
Date posted:	Thu Aug 9 09:45:10 PDT 2007
Patch name:	update/agraph-2.1/pfo009.001
Description:	Reduces the chance of running out of file handles by closing any index files that have never been used by a cursor once they have been merged.
Impact:	recommended

agraph patch
Date posted:	Thu Jul 19 10:40:04 PDT 2007
Patch name:	agraph/tutorial-files/kennedy.ntriples
Description:	This patch updates the tutorial file kennedy.ntriples. The initial ntriple file shipped with the distribution could not be used for the range query examples because its triples had objects that could not be encoded. The new file has the same information but its triples can be encoded and range queries will work correctly.
Impact:	recommended

agraph patch
Date posted:	Thu Jul 19 10:40:04 PDT 2007
Patch name:	agraph/agsrc-2_1.jar
Description:	The source package to the agraph-2_1.jar file released on Fri Jul 13 11:43:29 PDT 2007.
Impact:	recommended

agraph patch
Date posted:	Thu Jul 19 10:40:04 PDT 2007
Patch name:	update/agraph/2.1/pfo008.001
Description:	A call to twinqlSelect() was throwing an exception when the query produced an empty result.
Impact:	recommended

agraph patch
Date posted:	Fri Jul 13 11:43:29 PDT 2007
Patch name:	update/agraph/2.1/pfo007.001
Description:	Corrects a bug in all of the select-distinct macros that caused them to return duplicate results and/or inconsistent results. The bug only occurred when more than one variable was used in the result set.
Impact:	recommended

agraph patch
Date posted:	Fri Jul 13 11:43:29 PDT 2007
Patch name:	update/agraph/2.1/pfo006.001
Description:	Corrects a bug in get-triple-by-id wherein it would fail to return the correct triple for IDs less than 256 if the triple-store large.
Impact:	recommended

agraph patch
Date posted:	Fri Jul 13 11:43:29 PDT 2007
Patch name:	update/agraph/2.1/pfo005.001
Description:	Triple-stores created or opened with relative-pathnames such as (create-triple-store "./data") or (open-triple-store "data" :directory "./testing/") could cause AllegroGraph to lose track of the correct location of the triple-store and its data file. Triple-stores created with absolute path-names were, and continue to be, completely safe.
Impact:	recommended

agraph patch
Date posted:	Fri Jul 13 11:43:29 PDT 2007
Patch name:	agraph/agraph-2_1.jar
Description:	TopBraid Composer sometimes shows conflicting data when blank nodes are involved
Impact:	recommended

agraph patch
Date posted:	Fri Jul 13 11:43:29 PDT 2007
Patch name:	update/agraph/2.1/pfo004.001
Description:	Corrects a bug where the task-manager could be become confused when too many equivalent tasked were scheduled too quickly (for example, if the same triple-store was asked to check indices too often). When this happens, the triple-store in question would refuse to close because it was waiting for tasks that no longer existed to complete.
Impact:	recommended

agraph patch
Date posted:	Fri Jul 13 11:43:29 PDT 2007
Patch name:	update/agraph/2.1/pfo003.001
Description:	Corrects an indexing bug that caused an occasional triple in an index file to be duplicated and another triple dropped. Index files created in AllegroGraph 2.1 before this patch should be recreated after installing the patch. Executing the following form while the store is open will accomplish this: (progn (add-indices (drop-indices (triple-store-indices))) (index-all-triples :wait t)) Alternatively, the entire graph should be recreated.
Impact:	recommended

agraph patch
Date posted:	Fri Jul 13 11:43:29 PDT 2007
Patch name:	update/agraph/2.1/pdo002.001
Description:	Automatic indexing in the Java and HTTP interfaces interacts badly with triple store updates. This patch suppresses automatic indexing. We recommmend that applications call indexing steps explicitly when the triple store data is stable.
Impact:	recommended

agraph patch
Date posted:	Fri Jul 13 11:43:29 PDT 2007
Patch name:	update/agraph/2.1/pdo001.001
Description:	RDFterm-equal in SPARQL FILTERs doesn't correctly handle future-parts.
Impact:	recommended

Initial ACLID_lisp_build numbers

Shared library info: