DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=32460>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND� INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=32460 Summary: child stores of different type to parent aren't visible in child list Product: Slide Version: 2.1 Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Stores AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] This is a further refinement of an earlier workaround I made as part of defect 31492 to fix an exception from the DB2 jdbc driver. The upshot of this problem is that a child collection of a root jdbc store that is a mount point for another store does not have a uri in the URI table of the parent JDBC store because the metadata for the second store is kept in the nodestore of the second store and not the jdbc nodestore of the root store. eg. If "/" (root) is a jdbc store and "tx2" is a second store definition with scope "/files_2" and an XML descriptor nodestore and tx filesystem content store then the uri "/files_2" is not stored in the URI table of the jdbc nodestore of the root store even though the binding "/->/files_2" is kept in the BINDINGS table of the jdbc nodestore. This caused an exception when trying to insert a new binding into the DB2 BINDINGS table because it couldn't find a valid uri ID for the uri "/files_2" in the URI table. What I've done to fix this problem now is to detect when this error occurs (ie. when the child uri is not found in the URI table during an insert into the BINDING table) and have added code in the DB2 adapter to create a uri in the URI table for these children. This allows the binding to be inserted into the BINDING table with a valid child id so that the list of children is correctly generated and any searches on the table based on child id will match the value in the URI table. I will attach the patch. It will not affect other jdbc store implementations and will fix the problem as noted in this defect's summary for DB2 stores as well as the exception I was seeing prior to that. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
