Skip to content

Codepolice

  • ⤫

LINQ to SQL and the XML datatype

Posted by Judy Alvarez Posted on February 25, 2022March 3, 2022
0

Today i have done some stuff with LINQ to SQL and the xml data type from SQL Server 2005. I had some problem finding information about this and spent some hours figuring out how the insert/update/delete worked. Post a comment if you find something I’ve done wrong. This is mostly for my own reference.

Get data

var q = (from ec in Business.PostCalc. ExtraCompensation.Descendants(“compensation”)select new { id = ec.Attribute(“id”).Value,  code = ec.Element(“code”).Value,  amount = ec.Element(“amount”).Value,  description = ec.Element(“description”).Value }).ToList(); lwExtraCompensation.DataSource = q;lwExtraCompensation.DataBind();

Delete data

You should of course run SubmitChanges and so on in some method. I do this way so that we can save everything at once later.

XElement ec = Business.PostCalc.ExtraCompensation;XElement newExtraComp= new XElement(ec); newExtraComp.DescendantsAndSelf(“compensation”).Where(x => x.Attribute(“id”).Value.ToString() == e.CommandArgument.ToString()).First().Remove(); Business.PostCalc.ExtraCompensation = newExtraComp; txtDescription.Text = “”;txtAmount.Text = “”;txtCode.Text = “”; PostCalculationChanged(this, new EventArgs());

Update data

XElement ec = Business.PostCalc.ExtraCompensation; XElement newExtraCompensation = new XElement(ec); newExtraCompensation.Add(new XElement(“compensation”,new XElement(“description”, txtDescription.Text),new XElement(“amount”, txtAmount.Text),new XElement(“code”, txtCode.Text),new XAttribute(“id”, Guid.NewGuid()))); Business.PostCalc.ExtraCompensation = newExtraCompensation; txtDescription.Text = “”;txtAmount.Text = “”;txtCode.Text = “”; PostCalculationChanged(this, new EventArgs());
Categories: JavascriptTagged: asp net core cookie authentication, validation in asp net

Post navigation

Next Next post: LINQ to SQL and the XML datatype

Related Posts

  • Ways to remove event listeners

    #​624 — February 3, 2023 Read on the Web JavaScript Weekly You’ve Got Options for Removing Event Listeners — Unnecessary event listeners can cause all sorts of odd problems so it’s good to clean them up when you don’t need them anymore. How? There are several approaches and Alex looks at their pros and cons. (once

    Posted by Posted on February 3, 2023
    0
  • SQL in your JavaScript

    #​472 — February 2, 2023 Read on the Web AlaSQL.js 3.0: Isomorphic JavaScript SQL Database — A SQL database you can use in Node.js and the browser. The interesting bit, for me, is how it opens up the idea of using SQL to query JavaScript objects – as in this example. “The library adds the

    Posted by Posted on February 2, 2023
    0
  • Astro 2.0 and TypeScript 5.0 beta

    #​623 — January 27, 2023 Read on the Web JavaScript Weekly Astro 2.0: The Next-Gen ‘Islands’-Oriented Web Framework — 2.0 includes hybrid rendering (mixing of SSR and SSG outputs), type safety for Markdown & MDX, and an upgrade to Vite 4.0. Astro is worth exploring when performance is key as it works with popular frameworks

    Posted by Posted on January 27, 2023
    0
  • Automating the desktop with Node

    #​471 — January 26, 2023 Read on the Web Nut.js 3.0: Use Node for Desktop Automation — Take control of your desktop environment (Windows, macOS or Linux) from code with control over keyboard and pointer, plus you get some image matching possibilities too. Open source but with optional sponsor-only extension packages. GitHub repo and what’s new

    Posted by Posted on January 26, 2023
    0
  • Why document.write() is bad

    #​622 — January 20, 2023 Read on the Web JavaScript Weekly Why Not document.write()? — Many moons ago, document.write was a mainstay of client-side JavaScript code, but it’s long been considered a bad practice – why? Harry digs in, noting that it “guarantees both a blocking fetch and a blocking execution, which holds up the

    Posted by Posted on January 20, 2023
    0
  • We’re going on a memory leak hunt

    #​470 — January 19, 2023 Read on the Web Fixing a Memory Leak in a Production Node App — Kent encountered a variety of weird memory and CPU usage spikes in his Node-powered app and decided to figure out what was going on. This post walks through his complete journey, with plenty of side problems

    Posted by Posted on January 19, 2023
    0
Judy Alvarez

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Codepolice

  • Github
  • Atlassian
  • Flatlogic
  • Xero
  • Jetbrains
  • Figma
  • Ways to remove event listeners
  • SQL in your JavaScript
  • Astro 2.0 and TypeScript 5.0 beta
  • Automating the desktop with Node
  • Why document.write() is bad
https://flatlogic.com/generator
COPYRIGHT © 2023 - Codepolice