You’re perfectly fine making anything a class property, as long as you don’t intend on changing it.
Regarding your first question (the read only property), I have never had EOF write something to the DB without me explicitly telling it to do so, so you should be fine there as well—but you can certainly tick that box and get an extra layer of protection. Cheers, - hugi > On 31. okt. 2016, at 15:46, Theodore Petrosky <tedp...@yahoo.com> wrote: > > OK, so this table (users) is utilizing the login as the primary key. Since I > am only going to read and I can not change the database, I am going to have > to make the primary key a class property. There is no other way is there? > _______________________________________________ > 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/hugi%40karlmenn.is > > This email sent to h...@karlmenn.is _______________________________________________ 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
