On Dec 28, 2005, at 9:18 PM, James Affeld wrote:
> I really DON'T intend to start a religious war or diss
> anybody. I can barely spell SQL and have mysql up and
> running for another project (that doesn't support
> postgres but may 'someday'). It would be cool not to
> have to devote any of my few remaining brain cells to
> getting familiar with another db.
> I didn't see anything on the faq like "We HATE mysql,
> don't ask!", so I am asking. I'm just starting out,
> and will go ahead and use postgres. I just thought
> I'd squeak. If there's a chorus clamoring for mysql
> support, I'm in it. If I'm a soloist, so be it.
> Thanks for providing this tool - it looks very cool.
At this point, OpenNMS only supports PostgreSQL, as you have
noticed. We load a C-based shared library into the database to
support IPLIKE functionality, and we also have seven PL/SQL stored
procedures that we use as well. Some of the SQL code that we
generate might also be PostgreSQL-specific (I know that there is
definitely PostgreSQL-specific code in the installer, but you can
hack around that by setting up the databases by hand).
We want to be able to support multiple databases, in particular at
least one 100% Java database to make it easier for people to download
and install OpenNMS so they can kick the tires. Our plan is to do
this using Hibernate, which we want to do, and are currently
experimenting with, but none of the code uses Hibernate at this point.
At this point, unless you have familiarity with porting things from
one database to another, I would suggest that you just go with
PostgreSQL for OpenNMS. It doesn't take too much to backup and
restore the database (see the install guide for some examples), and
there doesn't tend to be much other maintenance that needs to be done
with the database now that we have cascading deletes and vacuumd to
do periodic clean-up.