Hi Erik,I think we actually agree, and the wording of my proposal was poor.On Dec 22, 2005, at 5:48 AM, [EMAIL PROTECTED] wrote:-1.In order, I prefer adding columns in SQL (SELECT) as appropriate, but onlyreturning to the user the columns/fields listed in setResult.I agree. Exactly what I meant to
[
http://issues.apache.org/jira/browse/JDO-264?page=comments#action_12361213 ]
Michelle Caisse commented on JDO-264:
-
Checked in patch2 with revision 358890.
> Fix issues in maven.xml preventing iut goals from running properly
>
Hi Erik,I'm afraid I don't have the energy to take on this addition to the spec, but I'd encourage you to see if you can find other like-minded folks to make a standard set of connection properties for failover.You can start a wiki page on the apache jdo site. You can use org.apache.jdo.options.fai
Hi Martin,
here is a simple test case showing the NoClassDefFoundError discussed in
JDO-194.I does a Class.forName for foo.bar when there is a class
foo.Bar. Attached you find a class Bar, please store it in a directory
foo. Class Main executes the Class.forName. I tried jdk 1.4.2_10 and
1.5.
[
http://issues.apache.org/jira/browse/JDO-194?page=comments#action_12361212 ]
Michael Bouschen commented on JDO-194:
--
Sorry Andy, this seems to be a JRE problem when running on Windows. I tried,
but the problem remains:
at java.lang.Class.forN
[ http://issues.apache.org/jira/browse/JDO-194?page=all ]
Michael Bouschen reassigned JDO-194:
Assign To: Michael Bouschen (was: Erik Bengtson)
> JPOX does not support implicit variables.
> -
>
> Key:
[ http://issues.apache.org/jira/browse/JDO-265?page=all ]
Andy Jefferson resolved JDO-265:
Resolution: Duplicate
Dup of JDO-248
> JPOX throws exception if default (empty) SELECT clause
> --
>
>
[ http://issues.apache.org/jira/browse/JDO-266?page=all ]
Andy Jefferson resolved JDO-266:
Resolution: Duplicate
Dup of JDO-249
> JPOX throws JDOFatalInternalException on SELECT new LongString(personid,
> lastname)
> --
JPOX throws JDOFatalInternalException on SELECT new LongString(personid,
lastname)
--
Key: JDO-266
URL: http://issues.apache.org/jira/browse/JDO-266
Project: JDO
Type: Bug
Components:
JPOX throws exception if default (empty) SELECT clause
--
Key: JDO-265
URL: http://issues.apache.org/jira/browse/JDO-265
Project: JDO
Type: Bug
Components: tck20
Reporter: Michelle Caisse
Assigned to: Andy
If you all have any comments on this discussion, please send them to general AT incubator.apache.org.Begin forwarded message:From: Leo Simons <[EMAIL PROTECTED]>Date: December 20, 2005 1:55:39 AM PSTTo: general@incubator.apache.orgSubject: Re: [VOTE] @domain for Incubator mailing listsReply-To: gen
Attendees: Miichelle Caisse, Martin Zaun, Michael Bouschen, Craig RussellAgenda:1. Test status (Michelle) datastore identity 562 tests; 10 failures, 17 errors; application identity 9 failures 17 errors; 4 of 28 configurations fail2. Graduation issues, changes to the repository (Craig) AI Craig: fol
Hi,
The standard allows setting up one data source per PMF. Failover mechanism to
recover from like "cannot obtain a connection" or "broken connections" are not
covered. Wouldn't be beneficial to cover such scenarios than upon failure will
switch to a backup data source?
Regards,
Erik Bengtson
Hi, David!
I'd like to share some of my ideas. We are
developing heavy stressed web applications based on
JDO. In each bi-di-relation, if the coder has to
assign both sides, the other side(usually a
collection) has to be loaded into memory and cause
much performance penalty. It's more efficie
14 matches
Mail list logo