Re: MS SQL Server and Deferred Constraints
Re: MS SQL Server and Deferred Constraints
- Subject: Re: MS SQL Server and Deferred Constraints
- From: Chuck Hill <email@hidden>
- Date: Wed, 27 Jun 2007 14:16:28 -0700
Not committed yet, just working on some better docs. You do want
docs, right? :-P
On Jun 27, 2007, at 2:13 PM, Dov Rosenberg wrote:
Which classes are these?
Dov Rosenberg
On 6/27/07 4:34 PM, "Chuck Hill" <email@hidden> wrote:
On Jun 27, 2007, at 1:08 PM, David Avendasora wrote:
You rock Chuck!
Is adding Wonder to my project the only way to do this?
Yes, but. Nothing in these classes rely on any Wonder "magic". Just
link in the framework (it does nothing by default) and use the
classes. I just put them in Wonder as it is a handy place to share
things.
You know, you're going to drag me kicking and screaming into the
new millennium. What's next Eclipse?
I can dream... :-P
Oh, and is that the name of the Class? I didn't realize you could
put spaces in there. Shouldn't it be "MSSQLsuxOr"? ;)
LOL
Chuck
On Jun 27, 2007, at 2:51 PM, Chuck Hill wrote:
Hi David,
I am just cleaning up code to handle this and also ordering the
DROP TABLE statements for MSSQL. It should be in Wonder in a few
hours.
MSSQL suxOr.
Chuck
On Jun 27, 2007, at 12:43 PM, David Avendasora wrote:
I know this issue has been discussed before, or at least eluded
to in posts, but I'm having problems with EOF inserting records
into related tables before it inserts them into the primary table
(I end up with Foreign key constraint SQL errors).
I'm using MS SQL Server (I know, but it is a requirement for the
application) and I need to have some way of making sure when
EOEditingContext.saveChanges() executes, it saves the records
bound for the primary table first. Here's my structure:
Routing<->>RoutingStep<->>RoutingComponent
Records for three are being instantiated in one EOEditingContext,
but when I call saveChanges() on it, sometimes (but not always)
it errors because it tries to insert RoutingComponent prior to
RoutingStep or RoutingStep prior to Routing into the database.
the end of the transaction. What is the most effective way to
work around this? I'm sure it has been addressed by people before
and if I'm just not finding it (I googled it). If it's out there,
just paste a link, if not, can someone share a code sample of how
they deal with it?
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve
specific problems.
http://www.global-village.net/products/practical_webobjects
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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