On Apr 17, 2012, at 7:25 PM, Pascal Robert wrote:
Le 2012-04-17 à 13:18, Ramsey Gurley a écrit :
Agreed. I like George's original suggestion. In the migration that creates
the required contract relationship, go through all the existing Shows and
create a default contract there. Keep
On Apr 16, 2012, at 6:16 PM, Ramsey Gurley wrote:
On Apr 16, 2012, at 9:13 AM, Johann Werner wrote:
Am 16.04.2012 um 16:43 schrieb Johan Henselmans:
On Apr 14, 2012, at 10:20 PM, Johan Henselmans wrote:
On Apr 14, 2012, at 4:17 PM, George Domurot wrote:
In your code snip,
Try refaulting the Show after you create the Contract to see if that helps.
ec.refaultObject(...)
On Apr 17, 2012, at 5:40 AM, Johan Henselmans wrote:
On Apr 16, 2012, at 6:16 PM, Ramsey Gurley wrote:
On Apr 16, 2012, at 9:13 AM, Johann Werner wrote:
Am 16.04.2012 um 16:43 schrieb
Doing all this in awakeFromFetch makes me feel kind of nervous.
Chuck
On 2012-04-17, at 9:41 AM, Kieran Kelleher wrote:
Try refaulting the Show after you create the Contract to see if that helps.
ec.refaultObject(...)
On Apr 17, 2012, at 5:40 AM, Johan Henselmans wrote:
On Apr 16,
I feel the same . but he can try it, test it and see what happens I guess.
If it was me, I would have just written a script to migrate the database and be
done with it.
On Apr 17, 2012, at 12:45 PM, Chuck Hill wrote:
Doing all this in awakeFromFetch makes me feel kind of nervous.
Agreed. I like George's original suggestion. In the migration that creates the
required contract relationship, go through all the existing Shows and create a
default contract there. Keep the data clean. Don't use awakeFromFetch for
tricks like this.
Think about it... What if the company hires
Le 2012-04-17 à 13:18, Ramsey Gurley a écrit :
Agreed. I like George's original suggestion. In the migration that creates
the required contract relationship, go through all the existing Shows and
create a default contract there. Keep the data clean. Don't use
awakeFromFetch for tricks
On Apr 14, 2012, at 10:20 PM, Johan Henselmans wrote:
On Apr 14, 2012, at 4:17 PM, George Domurot wrote:
In your code snip, you aren't adding the newContract object into the editing
context. To reduce errors like these, always use:
Thanks, after I posted the code I noticed that
Am 16.04.2012 um 16:43 schrieb Johan Henselmans:
On Apr 14, 2012, at 10:20 PM, Johan Henselmans wrote:
On Apr 14, 2012, at 4:17 PM, George Domurot wrote:
In your code snip, you aren't adding the newContract object into the
editing context. To reduce errors like these, always use:
On Apr 16, 2012, at 9:13 AM, Johann Werner wrote:
Am 16.04.2012 um 16:43 schrieb Johan Henselmans:
On Apr 14, 2012, at 10:20 PM, Johan Henselmans wrote:
On Apr 14, 2012, at 4:17 PM, George Domurot wrote:
In your code snip, you aren't adding the newContract object into the
In your code snip, you aren't adding the newContract object into the editing
context. To reduce errors like these, always use:
ERXEOControlUtilities.createAndInsertObject
I'd recommend not doing this in awakeFromFetch, but making this a step in your
migration to clean-up your DB/object graph.
On Apr 14, 2012, at 4:17 PM, George Domurot wrote:
In your code snip, you aren't adding the newContract object into the editing
context. To reduce errors like these, always use:
Thanks, after I posted the code I noticed that error and added
eo,insert(newContract)
It still does not want
12 matches
Mail list logo
