Re: How to fix "failed to provide new primary keys for..."?
Re: How to fix "failed to provide new primary keys for..."?
- Subject: Re: How to fix "failed to provide new primary keys for..."?
- From: Chuck Hill <email@hidden>
- Date: Mon, 17 Jan 2005 11:26:51 -0800
It is not that you have to do this, but that EOF/EModelers allows it in
case you really do need to do so (think legacy databases). EOF will
generate an integer PK for you without having it set as a class
property. In fact, it works better when it is not a class property.
You problem is that you are using PostgreSQL which is notorious for
being difficult to setup with WO. If you just want to get working, I'd
stick with FrontBase (my fave) or OpenBase which "just work". When you
are more experienced with WO, then go back to PostgreSQL if you want.
Otherwise, search the archives. You are not the first to experience
difficulties, not by a long shot!
Chuck
On Jan 17, 2005, at 10:09 AM, Ken Tozier wrote:
Seems kind of odd that you have to expose the PK field to the user and
force them to enter a number to save. Hopefully your suggestions will
do the trick.
--
Practical WebObjects - a book for intermediate WebObjects developers
who want to increase their overall knowledge of WebObjects, or those
who are trying to solve specific application development problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden