Relational-Object-XML-Object with LINQ to SQL & LINQ to XML

a-foton » Relational-Object-XML-Object with LINQ to SQL & LINQ to XML

a-foton » Relational-Object-XML-Object with LINQ to SQL & LINQ to XML — Mon, 28 Jul 2008 09:00:29 GMT

PingBack from http://blog.a-foton.ru/2008/07/relational-object-xml-object-with-linq-to-sql-linq-to-xml/

re: Relational-Object-XML-Object with LINQ to SQL & LINQ to XML

LINQ Master — Mon, 28 Jul 2008 19:53:58 GMT

Interesting solution. Might I suggest giving explanations of the abbreviations used, for people new to n-tier development?

<a href="http://blog.linqexchange.com">LINQ Exchange - Learn LINQ and Lambda Expressions</a>

re: Relational-Object-XML-Object with LINQ to SQL & LINQ to XML

Dinesh.Kulkarni — Tue, 29 Jul 2008 20:06:04 GMT

Sure thing LINQ Master! Just fixed the abbreviations. Thanks for the suggestion.

BTW, I deliberately cut out some explanatory text. I would really like people to copy-paste (and change) the code and not spend too much time reading the non-code text. No amount of explanation can equal the understanding gained from working code adapter to your scenario.

re: Relational-Object-XML-Object with LINQ to SQL & LINQ to XML

Ian Patrick Hughes — Wed, 30 Jul 2008 21:03:37 GMT

Awesome. I was just trying right something like this the other day for building a navigation bar from a cached xml object!

re: Relational-Object-XML-Object with LINQ to SQL & LINQ to XML

Rolandas — Tue, 05 Aug 2008 10:22:27 GMT

Why not just simply use XML serializer? It's more faster and the code becomes cleaner. Successfully done XML <-> Object <-> DB roundtrip. The only problem with LINQ is to get a KeyedCollection from ITable and EntitySet<T> keyed by the primary key (assuming only one primary key per table/view exists). Unfortunatelly, if XML contains updates of data, you need to have both DB data and your objects:

table.Attach(newRows[primaryKey], oldRow);

db.SubmitChanges();

re: Relational-Object-XML-Object with LINQ to SQL & LINQ to XML

Daniel Fisher (lennybacon) — Wed, 06 Aug 2008 20:14:26 GMT

Any reason why you did not use the DataContractSerializer? You could do the same within 4 lines of code ...

re: Relational-Object-XML-Object with LINQ to SQL & LINQ to XML

Dinesh.Kulkarni — Fri, 08 Aug 2008 16:54:22 GMT

The comments about using one of the serializers (DC or XML) is valid for the specific code fragments posted above. The serializers are great if you want to move all public or DataMember annotated members. If you want more control (e.g. encrypt a member) or want to check things declaratively, then the approach above provides more options.

But the main idea is to show you that LINQ to XML democratizes serializers. Writing one is a lot easier now than before.

Same applies to O->O mapping. You could have done that before too but now it is more declarative and compact.