> I looked back through my emails from when I backed this change out and
> can't figure out which test I regressed. The reason that I backed the
> change out rather than fix the problem is because we were in the middle of
> trying to cut a release. I'll open a new JIRA soon here and just recommit
>
I found because DBDictionary added NUMERIC into
> fixedSizeTypeNameSet. So postgres not generate (precision, scale).
> MySQLDictionary and SybaseDictionary removed NUMERIC from
> fixedSizeTypeNameSet and these two database support (precision,
> scale).
>
> I haven't view all Dic
NUMERIC into
fixedSizeTypeNameSet. So postgres not generate (precision, scale).
MySQLDictionary and SybaseDictionary removed NUMERIC from
fixedSizeTypeNameSet and these two database support (precision,
scale).
I haven't view all Dictionary class. Is there any reason to ignore
(precision, scal
On Sun, 17 May 2009 09:24:13 +0300
Georgi Naplatanov wrote:
> BTW HSQLDB supports memory based tables too. Is there a parameter in
> the dictionary for switching between memory and disk based (cached)
> tables ?
For connectio methods see the HSQLDB documentation[1] it tells you how
to connect to
9, Kevin Sutter wrote:
>
>
>> From: Kevin Sutter
>> Subject: Re: Database support
>> To: users@openjpa.apache.org
>> Date: Friday, May 15, 2009, 2:09 PM
>> Okay, so I'm looking at our stated
>> database support [1].� From this chart, I
>> would
idDB? The memory-based relational database?
>
> --- On Fri, 5/15/09, Kevin Sutter wrote:
>
> > From: Kevin Sutter
> > Subject: Re: Database support
> > To: users@openjpa.apache.org
> > Date: Friday, May 15, 2009, 2:09 PM
> > Okay, so I'm looking at our stated
Hi Kevin,
What about SolidDB? The memory-based relational database?
--- On Fri, 5/15/09, Kevin Sutter wrote:
> From: Kevin Sutter
> Subject: Re: Database support
> To: users@openjpa.apache.org
> Date: Friday, May 15, 2009, 2:09 PM
> Okay, so I'm looking at our stated
&
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 Op
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
> >
> >
gt; > 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
>
>
Ravi,
Volunteers for each database could be an alternative. Maybe volunteering
for database support would be a new requirement for committers? :-) Like
in your case, you seem to have a vested interest in Oracle. And, I tend
towards DB2 and Derby. But, what do we do about other mainstream
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 SQ
would help.
What do you think ?
Thanks,
Ravi.
-Original Message-
From: Kevin Sutter [mailto:kwsut...@gmail.com]
Sent: Wednesday, May 13, 2009 3:37 PM
To: d...@openjpa.apache.org; users@openjpa.apache.org
Subject: Database support
Hi,
I'm trolling... I'm looking for ideas on
hat 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
14 matches
Mail list logo
