From: RayLopez99 on
On Jan 3, 3:33 am, Arne Vajhøj <a...(a)vajhoej.dk> wrote:
> >> Updating, means writing, not reading.  A crash during that is very bad...
>
> > True enough I suppos, but I've usedXMLextensively (outside a DB
> > context) and I think a crash in the middle of a update (write) would
> > be rare.
>
> If loosing data being rare is good enough, then a lot of
> things is possible.
>
> But usually people care about their data.
>
> >        And I'm not sure that a crash in the middle of an UPDATE in
> > a DB (at the server end) would not corrupt the DB as well.
>
> The DB should recover fine (if it is a database server with a log
> file - MS SQLServer, IBM DB2, Oracle DB, Sybase ASE,
> MySQL with InnoDB tables, PostgreSQL etc.).
>
> That is what databases do.
>
> > BTW, in Silverlight, SQL is not supported (as of yet) so that' s
> > another reason to useXML.
>
> SL----web service----database
>
> works fine.

I bought a book by Papa called Data Driven Services for Silverlight2
that discusses setting up a web service for SL, and I was able to set
up and consume a simple web service. Thanks to you and A.G. of this
thread.

But I stand by my statement that XML is a cheap and easy way to mimic
a database. For example, nearly every example I see uses XML or hard
coded values, not a SQL query and a dB, to populate a list, GridView /
DataGrid, or combo box for example.

RL