JIRA DERBY-3009 created.
Regards,
Nick
-Original Message-
From: Williamson, Nick
Sent: 15 August 2007 09:53
To: Derby Discussion
Subject: RE: IJ out of memory
Thanks Kristian,
I'll visit the site and create an issue, attaching the script. Thanks
for doing the investig
Thanks Kristian,
I'll visit the site and create an issue, attaching the script. Thanks
for doing the investigation.
Regards,
Nick
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 15 August 2007 09:45
To: Derby Discussion
Subject: Re: IJ out of m
Regards,
Nick
-Original Message-
From: Bryan Pendleton [mailto:[EMAIL PROTECTED]
Sent: 14 August 2007 15:41
To: Derby Discussion
Subject: Re: IJ out of memory
Failed Statement is: ALTER TABLE logicproperty
ADD CONSTRAINT r_186
FOREIGN KEY
( zone_id )
REFERENCE
would help; at around 650k, I
think it's too big for the list. If anyone would like to see it, please
e-mail me off-list.
Regards,
Nick
-Original Message-
From: Bryan Pendleton [mailto:[EMAIL PROTECTED]
Sent: 14 August 2007 15:41
To: Derby Discussion
Subject: Re: IJ out
Failed Statement is: ALTER TABLE logicproperty
ADD CONSTRAINT r_186
FOREIGN KEY
( zone_id )
REFERENCES zone
ON DELETE CASCADE
You can include the foreign key constraints in the
initial table definition itself, instead of creating the
table and then adding the constraints to it later.
Thanks Kristian,
...and apologies for the lack of information. I knew as soon as I'd
posted that I should have said more about the environment...
My config is default AFAIK, with the exception that I have the error
logging set to 0. That said, I still get the OOME if I set error logging
back to t
Williamson, Nick wrote:
Hi all,
I'm experiencing java.lang.OutOfMemoryError when trying to create a
large schema (500+ tables, lots of constraints). Is there anything I can
do about it (perhaps by allocating more memory to IJ) or is it a bug?
Hello Nick,
You say nothing about configuration, s