Just to whine/whinge a little more,
If you simply remove the source-code directories from the class path, then EOF
can’t find the classes as defined in the EOModel, so what does EOF do? Throw an
exception? Nope. Just uses EOGenericRecord instead. Silently.
That would have gotten me around the i
> Either that or I’m doing something fundamentally wrong. Place your bets!
Okay all you people that bet on “SQL generation is busted” are out of luck!
Shockingly *I* was doing something wrong.
What? Nobody bet against it being my fault? Sigh.
Anyway, here’s what I was doing “wrong”:
We are us
On 2014-04-24, 8:05 AM, "David Avendasora" wrote:
Lack of good code hygiene beyond pretty formatting has now bit me.
I should have had the following like a real developer:
protected static ERXEnterpriseObjectCache cacheByPrimaryKey = null;
protected static ERXEnterpriseObjectCache cacheByPrimar
It’s in the previous email. Here again:
public static ERXEnterpriseObjectCache cacheByPrimaryKey = new
ERXEnterpriseObjectCache(Airport.ENTITY_NAME,
"primaryKey", // Cache Key
Still working on my first cup of coffee… is the issue here that you are suing a
static initializer on an EO? If so, I think you need to show it to us, or tell
us why. That is a bad thing to do if it touches any of EOF. It just is.
Chuck
On 2014-04-24, 8:42 AM, "David Avendasora" wrote:
O
On Apr 24, 2014, at 11:05 AM, David Avendasora
wrote:
> If ERXEnterpriseObjectCache breaks it, what else can?
That was *supposed* to be rhetorical. But, well, guess what? I can tell you at
least one other thing that breaks it:
ERXFrameworkPrincipal.setUpFrameworkPrincipalClass(Class)
Seri
This is now biting me.
I have the following:
public static ERXEnterpriseObjectCache cacheByPrimaryKey = new
ERXEnterpriseObjectCache(Airport.ENTITY_NAME,
"primaryKey", // Cache Key
Done. ;-)
On 02.02.2008, at 20:09, Anjo Krank wrote:
As WOLips just calls into the WO Derby plugin, I'd guess you better
log a bug with WO.
Cheers, Anjo
Am 02.02.2008 um 19:39 schrieb Sergio Sánchez Maffet:
does anybody know a quick workaround for the above mentioned issue.
Derby does no
As WOLips just calls into the WO Derby plugin, I'd guess you better
log a bug with WO.
Cheers, Anjo
Am 02.02.2008 um 19:39 schrieb Sergio Sánchez Maffet:
does anybody know a quick workaround for the above mentioned issue.
Derby does not support the cascade command in drop table statements,
Hi all,
does anybody know a quick workaround for the above mentioned issue.
Derby does not support the cascade command in drop table statements,
but the Entity Modeler in WOLips generates always the cascade command
which leads to a SQL syntax error if you execute the SQL without
modificat
Thanks Denis,
It works:)
Only one issue left for now;)
Xavier
Hi,
On May 2, 2007, at 4:58 PM, Chuck Hill wrote:
Bad jdbc2info in the model can do this. Have you changed the DB
or JDCB driver too? Is the jdbc2info in the model corrupted? Is
there some different external type for the
Hi,
On May 2, 2007, at 4:58 PM, Chuck Hill wrote:
Bad jdbc2info in the model can do this. Have you changed the DB or
JDCB driver too? Is the jdbc2info in the model corrupted? Is
there some different external type for these attributes?
Chuck
I had the same problem and have deleted the
Hi, still trying to get used to Eclipse:)
I'm editing an eomodel with a prototype. Everything is working as
expected as far as editing the model.
But when I try to generate the SQL for the model I got:
--
Error java.lang.Integer
java.lang.ClassCastException: java.lang.Integer
at
com.
13 matches
Mail list logo
