Re: T-Locking and Resolving

[Oliver Zeigermann]

While doing this: LinkNode has no ctor for bindings. This may make sense 
as it seems obsolete now. Can anyone confirm this?

Anyway, we should keep it for backward compatibility, right?

Oliver

Oliver Zeigermann wrote:

Oliver Zeigermann wrote:

Open issues.

1) All child store implementations (MySQL, JDBC, etc.) should save the
*binding* vectors instead of the children vector of ObjectNode.


This should mainly be the J2EE / JDBC store. This will be on my list!


I checked the implementation and it really seems easy to make this 
adaption.

I propose:

1.) A general change in DB schema: replace children table with a binding 
and a parentBinding table like this:

CREATE TABLE BINDING (
    URI_ID          id_type               NOT NULL
        REFERENCES  URI (URI_ID),
    CHILD_UURI_ID    id_type               NOT NULL
        REFERENCES  URI (URI_ID)
)
CREATE TABLE PARENT_BINDING (
    URI_ID          id_type               NOT NULL
        REFERENCES  URI (URI_ID),
    PARENT_UURI_ID    id_type               NOT NULL
        REFERENCES  URI (URI_ID)
)
2.) An update of StandardRDBMSAdapter to reflect the change in schema 
and usage of ctor ObjectNode(String uuri, Vector bindings, Vector 
parentBindings, Vector links).

I will do so if there are no objections,

Oliver



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
.





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]