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 get
errors at runtime in case of incorrect configuration, thus i tried
configuring indexes in repository...
Any idea for which direction i should go?
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.
Also, the following is a key issue:
Charles Anthony wrote:
The database always decides what indexes to use, never OJB !
What you should do to get OJB to use database indexes is use P6Spy or
the logtrace from your RDBMS, inspect the generated statements and
then set indices accordingly (so that OJB-generated SQL can use
indices).
There are some 3rd party tools to help you time Statement execution
times and give you hints for what to set your index on (eg [1], [2]).
Regards,
Martin
[1] IronGrid IronTrack - built on top of bundled P6Spy
Presents graphical trace, "culprits" and timeline of Statement times
http://www.irongrid.com/catalog/product_info.php?products_id=32
[2] Jahia SQL Profiler - integrates with P6Spy
Somewhat old and simpler than IronTrack, but can autogenerate index DDL
http://www.jahia.org/jahia/page377.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
