Greetings Markus, That would indeed work. One thing I have had some success with is a "semi-migratory" tool that uses D2W in combination with REST to remap the data outside the original store. It does not affect the original store, but it has some useful properties for organizing the data from the user's perspective.
I would also up the memory and test what portions break the batch faulting system. If none, count your blessings. If some, then there are some strategies I presented this last WOWODC that could help. I am currently cleaning up the audio for it, so that should help. Later, Daniel D. Beatty Computer Scientist, 474300D Detonation Sciences Branch On detail for Land Range Data Systems Branch At Exodus: (760)939-4040 MTTh 0800 to 1800 At Pearson: (760)939-7097 WF 0800 to 1600 iPhone: (806)438-6620 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Markus Ruggiero Sent: Monday, August 29, 2011 8:43 To: Ramsey Gurley Cc: [email protected] Dev Apple Subject: Re: Prevent NEW in D2W? 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 protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/daniel.beatty%40navy.mil This email sent to [email protected]
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
