Dominique,
Chuck's comment about identity columns cleared all my issues (basically, I changed the columns to integers). Aside from that, I have not had an issue with the plug-in using SQL Server 2008 R2.
From: Chuck Hill <email@hidden>
Sent: Friday, March 4, 2016 1:44 PM
To: Schoenenberger Dominique
Cc: Ress, David A; email@hidden
Subject: Re: SQL Server plugin framework
Hi Dominique,
I have not touched this in years, so it may need some updating.
Chuck
Hello,
I tried the MicrosoftPlugIn from WebObject distribution but it’s not working correctly.
In the post below, you mention a plugin you wrote and you provide a link. The link is not working anymore. Could you send me this code ?
Thanks,
Dominique
On 2014-11-25, 1:12 PM, "Ress, David A" wrote:
Good afternoon,
My current question is a development issue: I am using SQL Server and I cannot seem to find its plugin framework within the latest Wonder builds listed at
https://github.com/wocommunity/wonder. Could someone please tell me where I can find it?
A version that I made long ago is here
I thought that a newer version went into Wonder, but I could be wrong.
Without the plugin, I am getting the following error message when I attempt to insert a record from a form: "Cannot insert explicit values for identity column in table 'RxUser' when IDENTITY_INSERT is set to OFF." When I went into the EOModel to check
things out, I noticed the plugin was not set for the current model. That led me to looking for the MicrosoftPlugIn.framework.
Identity columns and EOF don’t play well. The database expected to populate the identity column when the row is committed and EOF needs to know the PK value before it commits. I have never used nor know anything about setting IDENTITY_INSERT to off.
I could possibly work. The plugin above does not do this.
Any suggestions for working with SQL Server in general would be appreciated. Coming from FrontBase, SQL Server seems like a 2-ton gorilla trying to lift a breadbox.
It is not my favourite database. My two pieces of advice are: don’t use identity columns and don’t lock on timestamp columns as SQL Server’s timestamps are less accurate than JDBC/EOF and this results in optimistic locking failures. Or did with the 2008
version.
Chuck
_______________________________________________
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
|