Andrew,
Another thing that's impressed me with OpenBase is the clustering
failover. I doubt many people have used this feature.
Any SQL written to any database in the cluster is automatically
propagated to other OpenBase databases in that cluster within five
seconds without any primary key collisions.
Additionally, if the master database fails your WebObjects app will
automatically begin using another database in the cluster (no code
needed to handle this case). Once the master database recovers, its
SQL, from the other databases, is updated and it resumes handling the
WO app's SQL.
Ciao,
Joe
On Dec 30, 2008, at 00:39:27, Andrew Lindesay wrote:
Hello Joe;
I think this problem may be slightly different as it is not
necessarily to do with PK's. My understanding is that
"OpenBasePKPlugIn" is there to get EOF to use the OPENBASE PK-
generation scheme rather than EO_PK_TABLE.
cheers.
I think I ran into the exact problem you mentioned about the
deadlock in OpenBase 10 using the default primary key generation.
Scott Keith advised me to compile the WO apps against the
OpenBasePKPlugin.framework which uses the OpenBaseJDBC.jar and,
even under heavy load, I've never had a problem using OB 10 with
the plugin. I just had to add a single line to my Application.java:
JDBCPlugIn
.setPlugInNameForSubprotocol
("com.webobjects.jdbcadaptor.OpenBasePKPlugIn", "openbase");
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
