Re: ConnectionPooling and the new parameter_collection.cs
I should mention that you should take the same precaution (using RefreshSchema) if there is any chance that the connection has changed in a way that would cause the commandbuilder to try to add a parameter to the collection after it has already done so. Maybe this is a bug.
This is what a stack trace looks like. In this scenario, da.Update has already been called several times, and if I insert a breakpoint in parameter_collection.cs I see that once is has been called, I can do several more Updates without it ever feeling the need to run the commandbuilder again, but on the Nth iteration it does this and breaks at the point in Add() where a parameter is added and it adds its hash to the hashtable.
Explanation? Should I file a bug report?
System.ArgumentException: Item has already been added. Key in dictionary: '?p3' Key being added: '?p3'
at System.Data.Common.DbDataAdapter.UpdatingRowStatusErrors(RowUpdatingEventArgs rowUpdatedEvent, DataRow dataRow)
at System.Data.Common.DbDataAdapter.Update(DataRow[] dataRows, DataTableMapping tableMapping)
at System.Data.Common.DbDataAdapter.UpdateFromDataTable(DataTable dataTable, DataTableMapping tableMapping)
at System.Data.Common.DbDataAdapter.Update(DataTable dataTable)
at MisMabel.EditOrders.AcceptOrder_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
Subject
Written By
Posted
November 22, 2006 01:19AM
Re: ConnectionPooling and the new parameter_collection.cs
November 22, 2006 12:10PM
December 01, 2006 04:32AM
December 01, 2006 08:33AM
December 01, 2006 09:25AM
December 01, 2006 10:11AM
December 05, 2006 09:56AM
December 05, 2006 10:02AM
December 16, 2006 12:28PM
December 17, 2006 12:57PM
December 05, 2006 03:01PM
December 06, 2006 02:52AM
December 06, 2006 07:33AM
December 06, 2006 09:45AM
December 06, 2006 11:21AM
December 07, 2006 02:47AM
December 07, 2006 08:21AM
December 07, 2006 07:08PM