> > Yes, at the moment, the limit is 64 columns.
>
> Kinda reminds me of a famous quote that went something like, "640k
> ought to be enough for anybody" :-)
LOL
---
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.ne
On Friday, October 10, 2003, at 10:52 AM, Alexey Loubyansky wrote:
Jason Essington wrote:
On Thursday, October 9, 2003, at 01:03 PM, Alexey Loubyansky wrote:
Jason Essington wrote:
I don't see anything immediately obvious about what I am doing
different here than with my other entities. All o
Jason Essington wrote:
On Thursday, October 9, 2003, at 01:03 PM, Alexey Loubyansky wrote:
Jason Essington wrote:
I don't see anything immediately obvious about what I am doing
different here than with my other entities. All of the others seem
happy enough (not pitching exceptions).
The only
On Thursday, October 9, 2003, at 01:03 PM, Alexey Loubyansky wrote:
Jason Essington wrote:
I don't see anything immediately obvious about what I am doing
different here than with my other entities. All of the others seem
happy enough (not pitching exceptions).
The only thing I can think that m
Jason Essington wrote:
I don't see anything immediately obvious about what I am doing different
here than with my other entities. All of the others seem happy enough
(not pitching exceptions).
The only thing I can think that may be causing a problem would be that
this entity has 111 persistent
I don't see anything immediately obvious about what I am doing
different here than with my other entities. All of the others seem
happy enough (not pitching exceptions).
The only thing I can think that may be causing a problem would be that
this entity has 111 persistent fields 6 container mana
Could you, please, provide detailed instructions how to reproduce it?
Thanks.
alex
Jason Essington wrote:
Alex
That didn't seem to fix it.
I don't know if this matters, but I am using the "Instance Per
Transaction CMP 2.x EntityBean" container configuration.
As a side note, I am also runni
Alex
That didn't seem to fix it.
I don't know if this matters, but I am using the "Instance Per
Transaction CMP 2.x EntityBean" container configuration.
As a side note, I am also running into a problem creating a new entity
where between ejbCreate and ejbPostCreate I receive:
java.lang.Ille
It was a bug that is fixed now. Could you, please, check it out in 24h?
Thanks much!
alex
Jason Essington wrote:
I am using a build from cvs as of this (10/7) morning. It claims to be RC5
the exact code that fails is
record.remove();
from the previous example.
From the debug output in the
I am using a build from cvs as of this (10/7) morning. It claims to be
RC5
the exact code that fails is
record.remove();
from the previous example.
From the debug output in the server.log file it appears that the
relationships are severed and the record and it's recently severed
relation
What JBoss version exactly are you using? 3.2.2RC5?
Could you post the exact code that fails?
Thanks,
alex
Jason Essington wrote:
I have some code that worked just fine in 3.2.1 but now it is having
trouble in the 3.2.2 branch of JBoss.
I am getting an SQLException when I try to remove an ent
11 matches
Mail list logo