Catarina Vieira Simoes wrote:
Francis Labrie wrote:
Catarina Vieira Simoes wrote:
[...]
The same thing happens when using the Postgresql and the
appropriate psql types as the stored procedure external types.
Any ideas about what's going on?
Unfortunately, EOPrototypes are not supported for stored procedure
(up to WebObject 5.3, maybe 5.4 as well). :-( I've already send
enhancement requests (rdar://4421477 and rdar://5084090) to get
this support in WebObjects two year ago.
I suggest you to fill up an enhancement request too at: <https://
bugreport.apple.com/>.
Thanks for your email.
I'm a bit confused here...
This means I have to create 2 different versions of the same stored
procedure, one for Oracle and one for Postgresql with the
respective types, in my model.
Unfortunately, yes... This is very sad and I hope next WebObjects
release will fix this. :-(
But still this doesn't explain the error message I got while
connecting to the Oracle database (using the Oracle prototype to
set the model external types) and using Oracle types in the
external types of the stored procedure attributes...
It seems your "jdbc2Info" dictionnary in the "connectionDictionary"
of your "index.eomodeld" model file is wrong or incomplete. I
strongly suspect it contains information for the PostgreSQL JDBC
driver...
To avoid such error when switching to different DBMS with the same
EOModel, I think it's safer to remove or empty the "jdbc2Info"
dictionnary.
And I'll fill a bug report.
Good. I hope Pierre will listen this time. ;-)
--
Francis Labrie
Saint-Bruno-de-Montarville, Quebec, Canada
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
