Hi,
I have a (probably simple) question about sorting collections:
I have 3 classes which I successfully mapped to OJB:
class Company {
Collection companyTeams;
public Collection getTeams() {
//???
}
}
class CompanyTeam {
Company c;
Team t;
int pos;
}
class Team {
String
Hi,
I have to deal with large objects with OJB and I sense I will get into
trouble with some performance issues if data is loaded each time objects
are created.
I saw some examples using the org.apache.ojb.broker.VirtualProxy class
but I dont manage to
Anybody having had such experience?
Hi Tino,
Sure you can do this. An example:
class-descriptor class=BuildingImpl table=tblPlnBuilding
...
collection-descriptor
name=rooms
element-class-ref=RoomImpl
orderby name=roomNo sort=ASC /
orderby name=roomSuffix sort=DESC /
inverse-foreignkey
Proxies are configured in the repository metadata:
http://db.apache.org/ojb/repository.html
=)
-Brian
On Apr 30, 2004, at 3:52 AM, Alexandre BOISSEAU wrote:
Hi,
I have to deal with large objects with OJB and I sense I will get into
trouble with some performance issues if data is loaded each
Hi,
being completely new to OJB I first tried to set up V1.0 RC6 and ran ant perf-test
successfully against the built in HSQL database.
As the intended target database is Oracle 9i in a second step I changed the profile to
be used to oracle9i in file build.properties.
It is not possible to
Hi Wolfram,
it seems to be a torque problem.
The tables creation failures only affect tables used in the junit test
suite, they are not necessary to run the 'perf-test' target (I assume no
liability ;-))
So you should be able to run perf-test anyhow
[torque-sql-exec] Failed to execute: ALTER
hi,
I have a question for OJB experts:
Is it possible to query with criteria that navigate through inherited
(possibly polymorphic) references?
It seems not because I have to redeclare all inherited reference in
subtypes to make these queries work.
I am facing problems with inherited references
hi edson, armin,
i checked it in.
jakob
Jakob Braeuchi wrote:
hi edson, armin,
imo the correct fix is as follows:
..
// ECER: assure it will notify all being removed, necessary for
RemovalAware classes...
if (isLoaded())
{
getData().clear();
}
..
Hi Jakob,
I'm not sure if this will solve the problem with removal aware list
implementation, because removal aware list only recognise loaded
objects. If clear was called on the proxy and data was not loaded the
objects will not be passed to the removal aware list.
So load data may be
hi armin,
you're right. but imo we should only force a load if the collection is removal
aware. i do not like the idea of loading objects to clear a list...
jakob
Armin Waibel wrote:
Hi Jakob,
I'm not sure if this will solve the problem with removal aware list
implementation, because
Jakob Braeuchi wrote:
hi armin,
you're right. but imo we should only force a load if the collection is
removal aware. i do not like the idea of loading objects to clear a list...
sounds good! To check the collection type seems the best solution...
Armin
jakob
Armin Waibel wrote:
Hi
hi armin,
i fixed it.
jakob
Armin Waibel wrote:
Jakob Braeuchi wrote:
hi armin,
you're right. but imo we should only force a load if the collection is
removal aware. i do not like the idea of loading objects to clear a
list...
sounds good! To check the collection type seems the best
hi loic,
there's a new feature to support pathHints per criteria. this could probably
help. btw the attachement got lost.
jakob
Loïc Péron wrote:
Hi,
I have a problem using patterns for querying
(case files attached as patch bellow for more precisions)
My query is two-level deep with two
13 matches
Mail list logo
