Pre-fetching

2015-02-21 Thread Robert B. Hanviriyapunt
I know how to set up pre fetching in a model based fetch spec. How does one do this programmatically? ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)

Re: Pre-fetching

2015-02-21 Thread Ken Anderson
setPrefetchingRelationshipKeyPaths(NSArray paths) On Feb 21, 2015, at 6:14 PM, Robert B. Hanviriyapunt roberth...@lstreetc.com wrote: I know how to set up pre fetching in a model based fetch spec. How does one do this programmatically? ___ Do

FrontBase triggers howto (was: Never save objects which don't pass a test (was: searching for a weird deletion))

2015-02-21 Thread OC
Hello there, after having played for a time with constraints, I have decided to use a trigger instead -- main reason is that I really want the validation performed on INSERT only; a constraint might get evaluated in other occassions, too. Nevertheless, I can't find a decent way of doing that

Re: Never save objects which don't pass a test (was: searching for a weird deletion)

2015-02-21 Thread OC
Chuck, On 20. 2. 2015, at 19:37, Chuck Hill ch...@gevityinc.com wrote: One way would be to twist the DB to do the complete restraint to me, something like to a pseudo-code “inserted_row.attr=MAX(SELECT attr FROM this_table WHERE another_attr.isValid) AND couple more similar conditions” --

Re: Never save objects which don't pass a test (was: searching for a weird deletion)

2015-02-21 Thread OC
Anyway, back to the original question -- On 20. 2. 2015, at 18:27, OC o...@ocs.cz wrote: Actually _this_ should not be weird, this should be quite a normal code; the only requirement is that check-and-save, i.e., conceptually, === if

Re: Never save objects which don't pass a test (was: searching for a weird deletion)

2015-02-21 Thread Chuck Hill
I think it is a fair expectation that EOF may not properly support optimistic locking. I am not even sure how to set it up properly. There are some methods on EOEditingContext and EODatabaseContext, and one the EODatabaseContext Delegate. Chuck On 2015-02-21, 3:42 AM, OC wrote: Anyway,

Re: Never save objects which don't pass a test (was: searching for a weird deletion)

2015-02-21 Thread Chuck Hill
I don’t know, I suggest asking on the FrontBase developers list. On 2015-02-21, 2:55 AM, OC wrote: Chuck, On 20. 2. 2015, at 19:37, Chuck Hill ch...@gevityinc.commailto:ch...@gevityinc.com wrote: One way would be to twist the DB to do the complete restraint to me, something like to a

Re: Never save objects which don't pass a test (was: searching for a weird deletion)

2015-02-21 Thread OC
Chuck, On 21. 2. 2015, at 20:09, Chuck Hill ch...@gevityinc.com wrote: I think it is a fair expectation that EOF may not properly support optimistic pessimistic, I guess? locking. I am not even sure how to set it up properly. There are some methods on EOEditingContext and

Re: Never save objects which don't pass a test (was: searching for a weird deletion)

2015-02-21 Thread Chuck Hill
On 2015-02-21, 11:17 AM, OC wrote: Chuck, On 21. 2. 2015, at 20:09, Chuck Hill ch...@gevityinc.commailto:ch...@gevityinc.com wrote: I think it is a fair expectation that EOF may not properly support optimistic pessimistic, I guess? Cough. Yes. locking. I am not even sure how to set it