Actually, exposing the PK is fine with EOF. Exposing an FK is what causes real problems.
On 2014-02-28, 1:47 PM, "Aaron Rosenzweig" wrote: Hi Ted, If you must expose the primary key… make a duplicate attribute with a Read format and make it read only. Look at page 41 of this document: https://developer.apple.com/legacy/library/documentation/WebObjects/UsingEOModeler/UsingEOModeler.pdf Exposing the PK as a class property could mess with the way EOF assigns the PK and it opens it up to possibly being modified. Aaron Rosenzweig / Chat 'n Bike<http://www.chatnbike.com> e: aa...@chatnbike.com<mailto:aa...@chatnbike.com> t: (301) 956-2319 [Chat 'n Bike] [Chat 'n Bike] On Feb 28, 2014, at 4:41 PM, Jesse Tayler <jtay...@oeinc.com<mailto:jtay...@oeinc.com>> wrote: generate a unique ID, if you don’t mind using HEX…. On Feb 28, 2014, at 4:32 PM, Chuck Hill <ch...@global-village.net<mailto:ch...@global-village.net>> 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 (Webobjects-dev@lists.apple.com<mailto:Webobjects-dev@lists.apple.com>) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/chill%40global-village.net This email sent to ch...@global-village.net<mailto:ch...@global-village.net> _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com<mailto:Webobjects-dev@lists.apple.com>) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/jtayler%40oeinc.com This email sent to jtay...@oeinc.com<mailto:jtay...@oeinc.com> _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com<mailto:Webobjects-dev@lists.apple.com>) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/aaron%40chatnbike.com This email sent to aa...@chatnbike.com<mailto:aa...@chatnbike.com>
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
