Back Home
  Frequently Asked Questions

For your edification.

  1. Can I use BugRat with JServ?
  2. What databases does BugRat work with?
  3. How do I configure BugRat?

  1. Can I use BugRat with JServ?
  2. Yes and no. You can use BugRat release 2.3.X or earlier. Note that these earlier releases do have bugs and deficiencies. However, the GJT, Apache, and others have run or are still running on 2.3.1b.

    That said, you really want to be running release 2.5 or better. Release 2.5 refactored for the servlet 2.2 API. This made a major difference in simplifying deployment and installation. Release 2.5 also greatly improved the code in terms of working with multiple database products. Finally several significant bugs were fixed. Alas, JServ can not run BugRat 2.5.

  3. What databases does BugRat work with?
  4. BugRat was designed and implemented on MySQL, a wonderful DB. BugRat has also been tested on Oracle. However, due to Oracle's less than standard way of dealing with large character fields, Oracle users must configure the servlets to recognize they are using Oracle, by adding one servlet initialization parameter to the web.xml config file. The parameter tells BugRat to use special code to handle string fields that can be larger than 4000 characters.

    Other databases are likely to work with BugRat if they have a good JDBC driver, and support SQL 92 or something close. Typically, the only thing needed is a proper schema file to create the tables used by BugRat.

  • How do I configure BugRat?
  • Almost anything that can be configured in BugRat is a property or other entry in the database. The best documentation for these entries is the SQL files 'defproperties.sql', 'defconfig.sql', and 'examplecats.sql'.


    Back Home