Log in

No account? Create an account

Previous Entry | Next Entry

SQL Stuff again. . .

So I got my select statement problems all taken care of, LEFT OUTER JOINS solved it all. I can now pull the data in my application and display it in a myriad of diffrent ways to make it usefull.

The next step is creating the ASP.NET 2.0 based DB Entry/Addition, and Editing and Deletion pages.

I'm having problems getting my head around the best way to do it.

I know there has got to be a simpler way to do this than doing a diffrent ASP.NET page for each portion of the process (Each Table) and clicking through the addition of one peice of data to each table that requires a diffrent peice of data.

A .net Transaction a la this page seems to be
the best way to go.

But how do I go about making it accept the form based (or whatever) based entry and tying that entered data into the 6 or so diffrent tables that it draws the information from.

Any thoughts?




( 1 comment — Leave a comment )
Nov. 26th, 2006 04:46 am (UTC)
transactions aren't really associated with .net, they're just putting a wrapper around a:


commit / rollback

they are a way of maintaining consistency and dealing with failure by issuing a rollback, or "undo". the commit of the data doesn't happen until the end, when all aspects take affect at once.

that said, there's no reason why you can't just get the form data from in your script and act on it across multiple tables. you aren't tied to a single table, and any query you can write can be acted on.

typically, i use something called table objects -- these are code-based versions of a table, tied to the table id. with this, i can make edits to an in memory object, and do a final commit at the end.

( 1 comment — Leave a comment )