Apple

id number description client
4000 Blue Dress Amex
3857 Blue Socks Chuck
3459 Blue Tie Ted
3460 Blue Blouse Visa

because the other numbers were made inActive (isActive = false).

On Feb 28, 2014, at 4:32 PM, Chuck Hill <email@hidden> wrote:

Does it mean anything to the user? I assume it does, otherwise, why would you show it? So what is going to happen when they see this:

id number description client

3456 Blue Dress Amex

3457 Blue Socks Chuck

3459 Blue Tie Ted

3460 Blue Blouse Visa

Where is 3458? Because that IS going to happen if you use the PK.

Chuck

On 2014-02-28, 1:25 PM, "Theodore Petrosky" wrote:

I need to create an Entity that will have a user visible id number. I thought I would just use the primaryKey but I recall reading so many times don't use the primaryKey for this.

This is a very simple Entity. It has a description, a Client, and a boolean (isActive). When the user views a list of these Entities, he/she will see:

id number    description     client

     3456         Blue Dress     Amex

when I insert a new Entity, I only need to supply the description and Client (from a popup). WO will supply the ID number. So why not use the primaryKey here? The user can never edit it. and none of these Entities will ever be deleted.

_______________________________________________

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

References:
	>exposing the primary key? (From: Theodore Petrosky <email@hidden>)
	>Re: exposing the primary key? (From: Chuck Hill <email@hidden>)