• 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
Re: Prevent NEW in D2W?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Prevent NEW in D2W?


  • Subject: Re: Prevent NEW in D2W?
  • From: Markus Ruggiero <email@hidden>
  • Date: Mon, 29 Aug 2011 17:43:06 +0200

Thanks Ramsey,

This is a completely standalone table with no relationships that contains one record with a couple attributes that define the configuration of the app. I was so deep into doing everything without programming that I missed the obvious. Your answer triggered the following solution: Having a simple page with a message and only a CANCEL button for the Create* pageConfiguration should solve my problem.

Thanks Ramsey, it is not the first time that your input has helped me further.💐
---markus---

On 29.08.2011, at 17:18, Ramsey Gurley wrote:

>
> On Aug 29, 2011, at 6:32 AM, Markus Ruggiero wrote:
>
>> Quick D2W question:
>>
>> isEntityEditable, isEntityDeletable, isEntityInspectable are all fine, but is there something like isEntityNewable?
>>
>> In other words: I have an entity with exactly one record that contains some global parameters to my app. The user must be able to update that one record but he must not be able to add a new record, there must be exactly one record with the same primary key at all times. How would I do this?
>>
>> Thanks
>> ---markus---
>
> This sounds like a model problem, not a view or controller problem.  If this is a one to one relationship, then model it that way.
>
> If the relationship is required, you can simply model it as a mandatory one-to-one joined on PKs and propagate the primary key.  EOF will automatically create the related object for you when your eo is created.
>
> If it is an optional one-to-one, then model it as two to-one relationships with an FK on each table.  Then in your entity class, override the inverseKeyForRelationship method to return the proper inverse relationship for each.
>
> If you have no control over the database schema and you need to do optional one-to-one with PKs then you're out of luck.  From your description, it sounds like doing it in the app is the wrong way to do it. To do it the wrong way, you'll need to provide your page level actions using a branch delegate and something like ERDControllerButton instead of using isEntity* since there is no key like isEntityNewable.  Either that, or you can build your own d2w page template and include an isEntityNewable conditional.
>
> Ramsey

 _______________________________________________
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: Prevent NEW in D2W?
      • From: David Avendasora <email@hidden>
    • RE: Prevent NEW in D2W?
      • From: "Beatty, Daniel D CIV NAVAIR, 474300D" <email@hidden>
References: 
 >Prevent NEW in D2W? (From: Markus Ruggiero <email@hidden>)
 >Re: Prevent NEW in D2W? (From: Ramsey Gurley <email@hidden>)

  • Prev by Date: RE: Need conceptual help with weird data model
  • Next by Date: RE: Prevent NEW in D2W?
  • Previous by thread: Re: Prevent NEW in D2W?
  • Next by thread: RE: Prevent NEW in D2W?
  • Index(es):
    • Date
    • Thread