• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
exposing the primary key?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

exposing the primary key?


  • Subject: exposing the primary key?
  • From: Theodore Petrosky <email@hidden>
  • Date: Fri, 28 Feb 2014 16:25:33 -0500

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


  • Follow-Ups:
    • Re: exposing the primary key?
      • From: Chuck Hill <email@hidden>
  • Prev by Date: Re: Unique Constraint Error
  • Next by Date: Re: exposing the primary key?
  • Previous by thread: Re: Unique Constraint Error
  • Next by thread: Re: exposing the primary key?
  • Index(es):
    • Date
    • Thread