I have just discovered Cayenne and would love to use it for a project
I am working on, but I can't find a way to do something which is
essential for the project: I want to be able to store and manipulate
XML objects in the database via JDBC 4. I'm currently using PostgreSQL
8.3 and have man
I just installed 8.10 Alpha5 and it seems that in Brasero
0.8.1-0ubuntu2, there is no possibility for verification. It does not
offer to verify the disc integrity. The only things which indicate post-
burn verification is the list in "Edit > Plugins" and the "Tools > Check
Integrity" functionality
Disregard the previous email, I spoke too soon. This is looking like a
bug in the MySQL/J driver; it's reporting the field as nullable when it
isn't.
-Original Message-
From: Scott Anderson [mailto:[EMAIL PROTECTED]
Sent: Friday, September 12, 2008 3:40 PM
To: user@cayenne.apache.org
Subj
In DbLoader.java, circa line 380, there is a reference to the NULLABLE
field. In the ResultSet I'm looking at, there's no such field - there is
however an IS_NULLABLE field.
-Original Message-
From: Tore Halset [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 28, 2008 3:19 PM
To: user@cay
On Fri, Sep 12, 2008 at 10:50 AM, Andrus Adamchik
<[EMAIL PROTECTED]> wrote:
> No. And I can't think of a reasonable solution that we can implement on our
> end.
At that point, I think it makes sense to push for a solution in Derby
as there it will
be hard to tell whether all code follows the rest
No. And I can't think of a reasonable solution that we can implement
on our end.
Andrus
On Sep 12, 2008, at 11:43 AM, Øyvind Harboe wrote:
On Fri, Sep 12, 2008 at 10:23 AM, Andrus Adamchik
<[EMAIL PROTECTED]> wrote:
This is a known problem on Derby. If this happens inside a
paginated list,
On Fri, Sep 12, 2008 at 10:23 AM, Andrus Adamchik
<[EMAIL PROTECTED]> wrote:
> This is a known problem on Derby. If this happens inside a paginated list,
> here is a workaround (that needs to be ported to the adapter at some point)
> :
>
> ((IncrementalFaultList) list).setMaxFetchSize(1000);
> // 1
On 12/09/2008, at 5:50 PM, Øyvind Harboe wrote:
I've got an obscure bug in our app that is caused by a stack
overflow with Derby.
The problem is that 'OR' is implemented recursively inside Derby, so
when using ExpressionFactoyr.inExp() w/a *long* list, the stack
overflows.
Can this be wor
This is a known problem on Derby. If this happens inside a paginated
list, here is a workaround (that needs to be ported to the adapter at
some point) :
((IncrementalFaultList) list).setMaxFetchSize(1000);
// 1000 is just a random #, you'll need to play with this parameter to
optimize it
/
I've got an obscure bug in our app that is caused by a stack
overflow with Derby.
The problem is that 'OR' is implemented recursively inside Derby, so
when using ExpressionFactoyr.inExp() w/a *long* list, the stack overflows.
Can this be worked around in the Cayenne Derby adapter?
Should it?
I
10 matches
Mail list logo
