Changes

In the experience of Matthew Barnson (the original author of this FAQ)We think that compared to other bug-tracking systems, though,Bugzilla offers superior performance on commodity hardware, better price (free!),more developer-friendly features (such as stored queries, email integration,and platform independence), improved scalability, greater flexibility,and superior ease-of-use when compared to commercial bugunder long-tracking software. If you happen to be a vendor for commercial bug-tracking software,and would like to submit a list of advantages your product has over Bugzilla,simply send it to <documentation@bugzilla.org>and we'd be happy to include the comparison in our documentation. ==Why doesn't Bugzilla offer this or that feature or compatibility with this other tracking software?==It may be that the support has not been built yet,or that you have not yet found it.While Bugzilla makes strides in usability, customizability, scalability,and user interface with each release,that doesn't mean it can't still use improvement! The best way to make an enhancement request is to file a bug at[https://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla bugzilla.mozilla.org]and set the Severity to 'enhancement'.Your 'request for enhancement' (RFE) will start out in the UNCONFIRMED state,and will stay there until someone with the ability to CONFIRM the bug reviews it.If that person feels it to be a good request that fits inwith Bugzilla's overall direction, the status will be changed to NEW;if not, they will probably explain why and set the bug to RESOLVED/WONTFIX.If someone else has made the same (or almost the same) request before,your request will be marked RESOLVED/DUPLICATE,and a pointer to the previous RFE will be added. Even if your RFE gets approved,that doesn't mean it's going to make it right into the next release;there are a limited number of developers,and a whole lot of RFEs... some of which are quite complex.If you're a code-hacking sort of person,you can help the project along by making a patch yourselfthat supports the functionality you require.If you have never contributed anything to Bugzilla before,please be sure to read the Developers' Guide and Contributors' Guidebefore going aheadterm usage.

* '''MySQL''': All Bugzilla versions support MySQL.* '''PostgreSQL''': Bugzilla 2.20 contains 22 and above contain complete, stable support for PostgreSQL.* '''Oracle''': Bugzilla 3.2 and above have experimental support for PostgreSQLOracle.* '''MS-SQL''': MS-SQL support is currently underway for Bugzilla 3.8.

Bugzilla 2.22 contains complete, stable Sybase support for PostgreSQL. As of this releaseis no longer being worked on, using PostgreSQL with Bugzilla should be as stable as using MySQL. If you experience any problems with PostgreSQL compatibilityand most likely will never happen, they will be taken as seriously as if you were running MySQLSybase lacks many features Bugzilla needs.

Red Hat once ran a version of Bugzilla that worked on Oracle,but that was long, long ago; that version (Bugzilla 2.8) ==My perl is now obsolete,insecure, located at /usr/local/bin/perl and totally unsupportednot /usr/bin/perl. In August of 2005, Wim Coekaerts (Director of Linux Engineering at Oracle Corporation) wrote Is there an easy to Dave Miller confirming change that Oracle intended to implement and support Bugzilla. Thanks to in all the help of some Oracle engineers, Bugzilla 3.2 is the first release to support Oracle.files that have this hard-coded?==

Sybase support The easiest way to get around this is no longer being worked on. Even if it eventually happens, it's VERY unlikely to work without the end-user-company having to stick create a few developers on making several manual changes. Sybase is just NOT very standards-compliant (despite all the hype), and it turned out that way too much had link from one to be changed to make it work -- like moving half of the application logic into stored procedures to get any kind of decent performance out of it.[httpsother://bugzilla.mozilla.org/show_bug.cgi?id=173130 Bug 173130] is the relevant bug.

[https: ln -s /usr/bugzilla.mozilla.orglocal/show_bug.cgi?id=237862 Bug 237862] is a good bug to read through if you'd like to see what progress is being made on general database compatibility.bin/perl /usr/bin/perl

perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl Sadly, this command-line won't work on Windows unless you also have Cygwin.However, MySQL comes with a binary called replace which can do the job:  C:\mysql\bin\replace "#!/usr/bincontrib/perl" "#!C:\perl\bin\perl" -- *.cgi *.pl

Once you've modified all your files,you'll also need ==Is there an easy way to modify change the t/002goodperl.t test,as it tests that all shebang lines are equal to /usr/bin/perl.(For more information on the test suite, please check outthe appropriate section in the Developers' Guide.)Having done this, run the test itself:Bugzilla cookie name?==

perl runtestsNo.pl 2 --verbose

to ensure that you've modified all the relevant filesYes. If using Apache on Windows, you can avoid the whole problemby setting the ScriptInterpreterSource directive You need to 'Registry'run Bugzilla 3.(If using Apache 2 0 or higher, set it to 'Registry-Strict'.)ScriptInterperterSource requires a registry entry"HKEY_CLASSES_ROOT\.cgi\Shell\ExecCGI\Command" to associate newer.cgi fileswith your perl executable.If one does not already exist,create it with a default value Later versions of "<full path to perl> -T %*",e.g. "C:\Perl\bin\perl.exe -T %*". Make sure you close out the registry before trying it again.An export of the registry entry is:Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\.cgi\Shell\ExecCGI\Command]@="c:\\perl\\bin\\perl.exe -T %*" <Put that in a .reg file and import it into your registry> ==Is there an easy way to change the Bugzilla cookie name?==At present, nogenerally have even better performance under mod_perl.

==Does bugzilla run Bugzilla work under mod_perlSELinux?==Yes. You need to run Bugzilla 3.0 or newer. We recommend Bugzilla 3.0.3 or higher as significant improvements have been made in memory consumption.

==How can On most modern versions of Fedora and RHEL, Bugzilla be made to will work fine under SELinux?==Unfortunately there are no step-by-step instructions, but as long as it is underneath the following URL contains hints on how to do it: http:<code>/var/fedora.redhat.comwww/docshtml/selinux-apache-fc3</sn-debugging-and-customizingcode> directory.htmlYou may have to run this command to make it work properly, though: