From: Mel Hatzis <hatzis@juniper.net>
To: help-gnats@gnu.org
Cc: Yngve Svendsen - Sun Norway <Yngve.Svendsen@sun.com>,
Hans-Albert Schneider <Hans-Albert@HA-Schneider.de>,
"Andrew J. Gray" <andrewg@gnu.org>,
Lars Henriksen <Lars.Henriksen@netman.dk>
Subject: database backend for GNATS
Date: Wed, 10 Mar 2004 05:28:00 -0000 [thread overview]
Message-ID: <40494528.6070802@juniper.net> (raw)
I've been working on extending GNATS to support various backend
datastores. It is my hope that this work can be rolled into
(or perhaps become the basis for) GNATS 4.1 or whatever the next
release may be (GNATS 5.0?).
To date, I have successfully completed the implementation
of a version of GNATS which can be configured to run with
an Oracle backend. I have managed to roll this out at the
company where I work where it has met with much success.
If you are interested in evaluating this work, you can download
it (and review the related documentation) from:
http://professional.juniper.net/gnats/
The approach I've taken is to separate out all the functionality
associated with access to the GNATS PR data repository into
a separate library....essentially creating a clean interface
between GNATS and it's data store. The front-end utilities
and applications such as Gnatsweb are unaffected...they
continue to work exactly the same.
Currently, there are two back ends: the standard flat-file
repository, and an Oracle-based backend. We have been using
the Oracle version at Juniper for six months, with tens of
thousands of PRs and hundreds of users.
The work is based on a snapshot of the 4.0 beta 2 source, though
all subsequent patches have been incorporated...so all the work
that went into GNATS 4.0 is included. As of today, all patches to
the CVS version of GNATS have been included in this project.
It is my hope that this work will be extended to support
additional SQL datastores such as MySQL and PostgreSQL.
I believe that this could now be accomplished without
expending a great deal of effort. I'm willing to provide
a template to anyone interested in pursuing this endevour
to get this work underway.
--
Mel Hatzis
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next reply other threads:[~2004-03-10 5:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 5:28 Mel Hatzis [this message]
2004-03-24 9:32 ` Yngve Svendsen
2004-03-24 16:33 ` Mel Hatzis
2004-03-26 13:20 ` Pankaj K Garg
2004-03-28 3:19 ` Andrew Gray
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40494528.6070802@juniper.net \
--to=hatzis@juniper.net \
--cc=Hans-Albert@HA-Schneider.de \
--cc=Lars.Henriksen@netman.dk \
--cc=Yngve.Svendsen@sun.com \
--cc=andrewg@gnu.org \
--cc=help-gnats@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).