ChangeLog 2.0 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162
  1. 2003-10-03 Diego Caravana <[email protected]>
  2. * SqlCommand.cs: no change.
  3. * SqlConnection.cs (Close): Added checks for null instance
  4. variables.
  5. * SqlParameter.cs (Direction): Now handles parameters of type
  6. ReturnValue and InputOutput.
  7. * SqlParameterCollection.cs (IndexOf(string)): Search for
  8. SqlParameter object in list is done by obtaining ParameterName
  9. attribute, not directly through list.IndexOf().
  10. 2003-08-22 Duncan Mak <[email protected]>
  11. * SqlCommand.cs (ExecuteNonQuery): Return
  12. Connection.Tds.RecordsAffected if it is successful. Patch from
  13. Jörg Rosenkranz <[email protected]>.
  14. This is part of a fix to bug #40315.
  15. 2003-08-20 Duncan Mak <[email protected]>
  16. * SqlConnectionPool.cs (ReleaseConnection): A patch from Joerg
  17. Rosenkranz <[email protected]>. Currently, if a connection is
  18. closed by an external event (network problem, etc.) it is pushed
  19. back into the connection pool. The next Open call retrieves this
  20. invalid connection which leads to exceptions when executing
  21. statements.
  22. This patch fixes this problem. This closes bug #47429.
  23. 2003-07-04 Miguel de Icaza <[email protected]>
  24. * SqlDataReader.cs: Added extra information to the exceptions
  25. thrown by all the GetXXXX methods.
  26. 2003-03-15 Daniel Morgan <[email protected]>
  27. * SqlConnection.cs: if Server in the ConnectionString
  28. is set to "(local", use "localhost" as the hostname
  29. to connect
  30. 2003-03-04 Gonzalo Paniagua Javier <[email protected]>
  31. * SqlException.cs: implemented GetObjectData ().
  32. 2003-02-16 Daniel Morgan <[email protected]>
  33. * ChangeLog: added this file
  34. * SqlConnection.cs: - parse data source for 3 possible uses:
  35. "Server=hostname",
  36. "Server=hostname\\instancename",
  37. "Server=hostname,port" and open the connection based on the
  38. resulting server name and port.
  39. - Added support for named instances
  40. by discovery of the sql server tcp port via the sql monitor (udp port 1434)
  41. thanks to Phillip Jerkins ([email protected]) contribution.
  42. Also, thanks to Gonzalo and Tim for their help with timeouts.