RE: Problem with self-referencing relationship

Not from me too. I'm VERY busy in my FULL time job. I will come back later this week. Erik Bengtson -Original Message- From: Andy Jefferson [mailto:[EMAIL PROTECTED] Sent: Monday, August 08, 2005 8:31 PM To: jdo-dev@db.apache.org Subject: Re: Problem with self-referencing

Re: Inheritance proposal

Hi, I discussed the inheritance proposal with Michael today and we came up with a couple of questions I added below. The following table describes the inheritance strategy setting for each class for the 5 inheritance mappings. I abbreviated the inheritance strategies: new - new-table, super

Patch for Detachable, PersistenceCapable, StateManager

For the benefit of anyone developing the TCK and thinking about using the latest API20 (with yesterdays changes) when running with JPOX : It won't work with current latest build of JPOX (so stick to your existing jdo2-api-2.0-SNAPSHOT.jar) JPOX CVS has now been updated and the next nightly

Re: Inheritance proposal

Hi Michael(s), Not fully read your proposal, so can't comment on the rest ... - Does JDO require a inheritance element for classes in an inheritance hierarchy? If not, is there a default? The same questions apply to the strategy attribute inside of the inheritance element. You don't need to

Running a single test in fostore20 (was Re: Problem with self-referencing relationship)

Hi, [...] I heard you mentioning on the conference call that i could run an individual test in maven, could you please tell me how to do that? It depends on which project you're running. The TCK can run a single configuration (combination of database, test data, and test program. In the

Re: Inheritance proposal

Hi Andy, Hi Michael(s), Not fully read your proposal, so can't comment on the rest ... - Does JDO require a inheritance element for classes in an inheritance hierarchy? If not, is there a default? The same questions apply to the strategy attribute inside of the inheritance element. You

Re: Problem with self-referencing relationship

Hi Andy, I can run companyNoRelationships.conf several times without reinstalling the schema. The result is always the same: SQL Exception: Column name 'DATASTOREIDENTITY0.PERSONS.DATASTORE_IDENTITY' is in more than one table in the FROM list. This is JDO-93. I cannot reproduce JDO-116.

Re: Inheritance proposal

Suppose there are two non-abstract persistence-capable classes A and B. Class B extends A. Both explicitly define the inheritance strategy new-table. Class A maps to table TA and B maps to table TB. Then there are still two scenarios possible, depending on where to store the inherited fields

Re: Problem with self-referencing relationship

I can run companyNoRelationships.conf several times without reinstalling the schema. The result is always the same: Hi Michael, I get the same as you, today! but certainly didn't yesterday. Since I can't reproduce it myself now, someone please just close the issue (JIRA-116) and if I find

Re: Inheritance proposal

Hi Andy, thanks for the info! You are right, I forgot that I have the add field elements for the inherited fields. Regards Michael Suppose there are two non-abstract persistence-capable classes A and B. Class B extends A. Both explicitly define the inheritance strategy new-table. Class A

Re: Antlr 2.7.5

Hi, I changed the antlr dependency to version 2.7.5, because this version is available on ibiblio. So there is no need anymore to manually copy the antlr jar to the local maven repository. Regards Michael Hi Brian, hi Craig, as Craig pointed out, we had a non-standard way to support

Re: Cleaning up the datastore in tearDown

Minor point, but I would suggest doing it in setUp() for a couple reasons: * You know datastore is in good state before test runs instead of after * You can examine datastore state afterwards to double check things manually * If things go wrong during the test, the evidence isn't erased On