On 10/07/2007, at 12:35 PM, Peter Vandoros wrote:
I've seen this issue and it has come down to your eomodel being
inconsistent or the JDBC plug-in not finding the details for a
column in the JDBC typeInfo.
Things to check:
1. Make sure that the JDBC TypeInfo (jdbc2Info) defines all the
attributes column types in your entity.
2. Make sure you have "capitalizeTypeNames=true" in your jdbc
connection url for MySQL.
3. If you are using prototypes, make sure that they have been
initialised and your entity is actually using them. Also make sure
that you aren't using the prototype definitions of a different
DBMS. eg. using PostgrSQL prototype definitions with MySQL.
Thanks Peter, yes it seems to have been resolved now. There was a
prototype column defined for MySQL that wasn't in the generic
prototypes model.
with regards,
--
Lachlan Deck
_______________________________________________
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]
