Feature #1498
Feature #1478: write the "Runtime Installation, Configuration and Administration Guide"
finish/write the "Database" section of the Directory chapter
0%
History
#1 Updated by Greg Shah almost 12 years ago
Please cleanup/improve the database_cfg.odt chapter in the p2j_docs/runtime_installation_configuration_and_administration_guide/ project. The chapter has some content and examples but it needs lots of work. See my GES: notes in this chapter for details.
#2 Updated by Costin Savin almost 12 years ago
- Status changed from New to WIP
- Assignee set to Costin Savin
#3 Updated by Costin Savin almost 12 years ago
While searching info about the parameter prepareThreshold I assumed it refers to server prepared statements threshold-> number of times a statement is called before the query will be used as a named query (in order to optimize queries that are used more often), saving the execution plan at the database server.
Is this correct? I haven't found usage of the parameter inside any class of the p2j project.
#4 Updated by Eric Faulhaber almost 12 years ago
Regarding prepareThreshold...
Is this correct? I haven't found usage of the parameter inside any class of the p2j project.
Yes, this is correct. The parameter isn't used in a class, it is read from the directory along with other Hibernate connection properties at server startup and passed through to Hibernate for later use when getting a database connection. See com.goldencode.p2j.persist.DatabaseManager.readHibernateProperties().
#5 Updated by Costin Savin almost 12 years ago
What is "dirty" parameter (integer) of ../p2j/lock_manager/ used for?
(The best guess from searching related info would be that it has to dirty reading -> number of times you can read a lock object)