Okay, so I'm looking at our stated database support [1]. From this chart, I would divide up the databases into the following categories. The "Not Currently Covered" category is where I would focus my phishing efforts first. Any discussion?
Covered Interest by members of OpenJPA Community ======================================= o Derby o DB2 o Informix o Oracle o MS SQL Server ??? o Sybase ??? Not Currently Covered Interest by members of OpenJPA Community ================================================= o MySQL o PostgreSQL o H2 o HSQLDB (Hypersonic) o Firebird ??? Are these still required? ================= o Borland Interbase o Borland JDataStore o Empress o Intersystems Cache o MS Access o MS Visual FoxPro o Pointbase Thanks, Kevin [1] http://openjpa.apache.org/builds/latest/docs/manual/manual.html#dbsupport On Thu, May 14, 2009 at 10:01 AM, David Beer <[email protected]>wrote: > Hi Kevin > > Some database vendors usually have some sort of universal contact which > might be the best way of going about it. Posting a one of message to > support forums might well be an idea that could work. > > David > > On Thu, 14 May 2009 08:46:03 -0500 Kevin Sutter > <[email protected]> wrote: > > > Hi David, > > > > On Wed, May 13, 2009 at 5:10 PM, David Beer > > <[email protected]>wrote: > > > > > Hi Kevin > > > > > > I currently use OpenJPA with the H2 database for my embeded > > > programs, and will be considering MySQL for larger scale programs. > > > I think that the more database vendors or suppliers we can get > > > links with the better for both sides. I am happily using H2 with > > > OpenJPA but there were some features I had to ask about and how to > > > work with OenJPA. > > > > > > So my point is that we need a way of getting committers or users > > > from both sides to help so we need a way of maybe certifying a > > > database version. > > > > > > It sounds like we're on the same page. The tricky part is signing up > > this help and support from these database vendors and users groups. > > Maybe I should just post to these vendor's user forums and ask for > > some support. Just go phishing... :-) > > > > Kevin > > > > > > > > > > > > > Jut my thoughts. > > > > > > David > > > > > > On Wed, 13 May 2009 16:36:53 -0500 Kevin Sutter > > > <[email protected]> wrote: > > > > > > > Hi, > > > > I'm trolling... I'm looking for ideas on how we can better > > > > integrate with the various database vendors. Many of us > > > > committers have our own "favorite" databases due to our > > > > employers' needs. But, what about the MySQL, or Postgres, or SQL > > > > Server, or pick your favorite databases? I know we have had some > > > > interest from these database vendors on our users and dev forums, > > > > but I'm looking for ways to get these vendors more involved. > > > > When they produce a new version of their database, it would be > > > > great to announce OpenJPA support. And, if they have new > > > > features to take advantage of, that would be even better. > > > > > > > > Everybody's development and tests teams are limited. I understand > > > > that. But, I'm looking for ideas on how we can work together to > > > > accomplish this task. I'm going to cross post on both users and > > > > dev forums to see if there any lurkers that might have some ideas. > > > > > > > > Just to provide a real world example... I was just pinged about > > > > MS SQL Server 2008 support. Our OpenJPA manual only documents SQL > > > > Server 2005 support. I don't have experience with SQL Server. > > > > So, it made me think how we could improve this aspect of our > > > > OpenJPA database support. > > > > > > > > Any thoughts? > > > > > > > > Kevin > > > > > > > >
