Philippe Guillard wrote:
Then i red somthing i should read before in FAQ section 3.3 I recommend
to not use JDO now, but to use the existing ODMG api for the time being
and wonder if this would affect my problem too...
Any suggestion / what i should do next?
If you have any doubts about the
Thanks,
Excuse for my ignorance, 2 last questions:
- In the JPOX case it means using JPOX instead of OJB, right?
- Apache licensed JDO 2.0 implementation is scheduled for OJB 2.0. Is
there info somewhere about the schedule? (In that case i would wait, i'm
not in production yet)
Regards,
Philippe Guillard wrote:
Excuse for my ignorance, 2 last questions:
- In the JPOX case it means using JPOX instead of OJB, right?
Yes, that's right - JPOX != OJB product and JPOX currently have a
free-standing JDO implementation (as opposed to OJB's RI plug-in).
- Apache licensed JDO 2.0
Thanks Martin.
Martin Kalén wrote:
Philippe Guillard wrote:
Excuse for my ignorance, 2 last questions:
- In the JPOX case it means using JPOX instead of OJB, right?
Yes, that's right - JPOX != OJB product and JPOX currently have a
free-standing JDO implementation (as opposed to OJB's RI
]
Sent: 03 June 2005 09:29
To: OJB Users List
Subject: Re: JDO Query / indexed column
Hi all,
Really strange, this summurizes exactly my problem:
Using JDOQuery, my database index is not used query needs 6/7/8s to
commit on big table,
logs from MySql says:
SELECT A0.ZIP,. FROM USAZIP A0
Hi all,
Really strange, this summurizes exactly my problem:
Using JDOQuery, my database index is not used query needs 6/7/8s to
commit on big table,
logs from MySql says:
SELECT A0.ZIP,. FROM USAZIP A0
BUT using OJB Query, i get instantly the result.
logs from MySql says
SELECT
: Philippe Guillard [mailto:[EMAIL PROTECTED]
Sent: 03 June 2005 09:29
To: OJB Users List
Subject: Re: JDO Query / indexed column
Hi all,
Really strange, this summurizes exactly my problem:
Using JDOQuery, my database index is not used query needs 6/7/8s to
commit on big table,
logs from MySql says
Thanks a lot Martin, i'll give a try..
Phil
Martin Kalén wrote:
Philippe Guillard wrote:
Thanks Charles,
Unfortunately i get the same result without parameter. ( I use JDO
1.01 form Sun, OJB as integrated in cocoon framework).
You guess right i 've built the DB by hand before and adapted
Philippe Guillard wrote:
Thanks Charles,
Unfortunately i get the same result without parameter. ( I use JDO 1.01
form Sun, OJB as integrated in cocoon framework).
You guess right i 've built the DB by hand before and adapted a
repository later. It is not supposed to be used at runtime, but i
Martin Kalén wrote:
The index-descriptor is (as Charles pointed out) only used if you generate
DDL/SQL with OJB using Torque.
If you create your database by hand, you can remove all index-descriptor
attributes to get a cleaner OJB repository.
Clarification: The index-descriptor attribute is
Hi Phillipe,
The database always decides what indexes to use, never OJB ! OJB knows
nothing about indexes (the repository.xml entry is, or used to be, used to
generate the SQL/DDL to create the tables in the database. It isn't used at
runtime)
The SQL query that has been generated *doesn't* use
Thanks Charles,
Unfortunately i get the same result without parameter. ( I use JDO 1.01
form Sun, OJB as integrated in cocoon framework).
You guess right i 've built the DB by hand before and adapted a
repository later. It is not supposed to be used at runtime, but i get
errors at runtime in
12 matches
Mail list logo
