From: Anjo K. <kr...@lo...> - 2007-02-28 23:44:47
|
Am 01.03.2007 um 00:34 schrieb Chuck Hill: > Something is messed up in the model. I have seen things like that > happen when the jdbc2info stored in the EOModel was wrong. I have > also see incorrect valueTypes cause that. Check the connection > dictionary and the prototypes being used. Uh... we remove the jdbc2info dict on startup, so the values you see in EOM may not be the current one in the app. Try: -DdbRemoveJdbc2InfoGLOBAL=false in your launch args. Cheers, Anjo |