Hi,
I have I inheritance-problem. I want to map two classes to one table.
They are defined as followed:
class A {
int id;
protected String ojbConcreteClass;
// some attributes
}
class B extends A {
// some additional attributes
}
I created class-descriptors
Tino Schöllhorn wrote:
Hi,
I have I inheritance-problem. I want to map two classes to one table.
They are defined as followed:
class A {
int id;
protected String ojbConcreteClass;
// some attributes
}
class B extends A {
// some additional attributes
}
I created
Hi Oleg
here are the informations.
First, the data before the test (I include only the ids, the tables are
quite long):
ID ID_DOSSIER
totoMon Jun 14 08:35:27 CEST 2004 2870475
totoWed Jun 09 17:05:30 CEST 2004 2870475
510183102
Tino Schöllhorn wrote:
thanks now it works. But why do I have to map the attributes of the
superclass in the subclass again? Is this intended or is the
inheritance of descriptors a not yet enhancement?
Yes, this is by intention because you don't necessarily want to have all
persistent fields of
Hi,
unfortunately I still have one problem:
I use a xml-parser to pre-validate the repository.xml-file. This Parser
now complains that field-descriptors cannot be used when using extent. I
checked that with the DTD and I think it is correct:
!ELEMENT class-descriptor
((documentation?,
Tino Schöllhorn wrote:
Hi,
unfortunately I still have one problem:
I use a xml-parser to pre-validate the repository.xml-file. This
Parser now complains that field-descriptors cannot be used when using
extent. I checked that with the DTD and I think it is correct:
!ELEMENT class-descriptor
Hi!
Suppose I've to do something in the DB launching directly an SQL statement,
bypassing OJB how can I do it?
And how to prevent problems with the object cache of OJB?
ie: if a launch UPDATE costs_table SET cost = cost + 10, but some record has
already been loaded in memory by OJB...how
Yes, I am using ODMG.
I have downloaded RC7 this morning and tried again. The collection proxy
works fine, but I still have problems with the reference proxies. Here is
the code snippet I am executing :
public void testModificationDirect() {
String idDossier =
I was just poking around ODMG to fix the collection proxy thing, can
nose around about regular references.
I probably won't get a chance to look at it until tomorrow night at the
earliest, so if anyone else has a moment sooner... =)
Thank you for finding the problems!
-Brian
On Jun 14, 2004,
The OJB team would like to announce the release of Apache
Object/Relational Bridge (OJB) 1.0rc7.
This release will hopefully be the final release candidate before
version 1.0. If no major problems
are discovered, OJB 1.0 will be released in one week.
DOWNLOADS
http://db.apache.org/builds/ojb/
Hi,
I think this topic has been discussed before. But I am not sure what the
current status is:
I have two classes A and B. A has a Collection of Bs. Now if I delete a
B object which is part of a Collection of an A object the B object is
correctly deleted in the database and is also removed
Armin,
I have tried my code with rc7 and I still have the problem I described.
Looking at the test case you have written, it seems to produce the results
I would like. That is, your code does not return null objects for objects
that should be retrieved via anonymous foreign keys contained
I'm wondering if the listed KNOWN ISSUES will be resolved for 1.0? It
sounds like not, and at least one of them worries me.
Brian - odmg-api: It is not possible to exchange objects in 1:n
Brian references.
I'm not sure what this means. Is it a new problem?
Brian - odmg-api:
Hi Steve,
Steve Clark wrote:
I'm wondering if the listed KNOWN ISSUES will be resolved for 1.0?
We try to list all unsolved major issues for 1.0 (we are open source,
thus there is no reason for keep quiet about known issue).
We will try to fix these problems ASAP in a 1.0x release.
It
sounds
Brian - odmg-api: Creation of m:n relation only works when
Brian objects created step by step (or use PB-api as workaround),
Brian persist a whole object graph doesn't work. On delete of
Brian collection objects from a m:n relation objects will be
Brian deleted from the
Hi all
As many knowns sequences are not implemented by all db provider.
Special mention to DB2 AS400 in my jobs. I was looking to
SequenceManagerStoredProcedureImpl sequence manager solution. Quite
pleasant by not implemented within PlatformDb2Impl just for M$SQLServer
...
I'd like to
Hi Tino,
Have you an unique Id in class A? Try this example (I have followed the
OJB Tutorial ):
class-descriptor class=ojb.test.A table=T_AB
isolation-level=read-uncommitted accept-locks=true refresh=true
extent-class class-ref=ojb.test.B /
field-descriptor name=oid
Hello,
I have a simple unit test class :
public static String id;
public AppointmentDelegateTest(String arg0)
throws Exception
{
super(arg0);
Appointment appointment = new Appointment();
User user = new User();
appointment.setUser(user);
appointment.setCreationDate( new
there i am again , setting collection-class=managableList solved all the
deleteting so forget about my question please. I still see Result of
getTableAlias(): null though , what does it mean?
[org.apache.ojb.broker.accesslayer.sql.SqlGeneratorDefaultImpl] DEBUG:
SQL:INSERT INTO Appointment
19 matches
Mail list logo
