FW: [Mono-list] DbDataAdapter.Fill patch

[A Rafael D Teixeira]

>From: ville <ville.palo@koti.soon.fi>
>To: "Daniel Morgan" <danmorg@sc.rr.com>
>Subject: Re: FW: [Mono-list] DbDataAdapter.Fill patch
>
>Hi Daniel!
>
>I think Rodrigo or Tim Coleman knows better, but I can try something:
>(if) There could be more than one datasource in one DataSet so this is
>IMHO more reasonable way. But I'm not realy sure why "one DataAdapter
>cannot be be able to perform all the needed updates."?
>
>
>MSDN says: "Additional result sets are named by appending integral
>values to the specified table name (for example, "Table", "Table1",
>"Table2", and so on.)." That is you cant be sure the name of the table
>is "Table".

That is for additional result sets sent by the SAME SqlCommand. That occurs 
when you call a Stored Procedure that executes many SELECTs, and led me to 
many headaches, many of them, about table ordering ,when coupled with 
typed-datasets.

BTW, these kind of stored procedures, make the DataAdapter non-updatable 
(the ADO.NET wizard refuses to generate Insert, Delete Update SQLCommands, 
because he can't figure primary keys, and such).
>
>MSDN also says: "The Fill operation then adds the rows to destination
>DataTable objects in the DataSet, creating the DataTable objects if
>they do not already exist."

Again, that's inside a SINGLE execution of the SelectSqlCommand, for that 
adapter.

Happy Hackings,

Rafael Teixeira
Brazilian Polymath
Mono, MonoQLE Hacker





_________________________________________________________________
MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. 
http://join.msn.com/?page=features/virus