SQL is SO OLD
How old is SQL? Older than my grandmother! (Almost)
Granted today's standards have changed over time from the use of inline SQL to Stored Procedures, but the change that I propose would also cut the length of our Stored Procedures in HALF.
What I want is simple: combine UPDATE and INSERT into one statement.
There's many different options here, but I believe the best way would be to simply add an additional parameter to the UPDATE statement that would basically let the server KNOW to INSERT the record if it didn't already exist.
UPDATEINSERT TableName SET Field1=data1,Field2=data2 WHERE ID=1 ??
UPDATE OR INSERT TableName ...
UPDATE TableName SET .. WHERE ... IF NOT EXIST INSERT
At least make INSERT work the same:
INSERT INTO TableName SET Field1=data1,Field2=data2.
At least then we could simple swap INSERT INTO with UPDATE and add a WHERE.
Any one else have any better ideas?
Comment Notification
If you would like to receive an email when updates are made to this post, please register here
Subscribe to this post's comments using
Comments
Leave a Comment
About dwalker
David Walker has over 15 years experience in application development with over 50% of that employed as a consultant with companies such as: Texaco, Bank of Oklahoma, Winner Communications (ESPN.com) and IBM Global Services. At the age of 14, he began his application development ambitions with a Commodore 64, BASIC, and a 300 baud modem. Even at that early age, he primarily focused on two specific application types: multi-user communities and database applications.
His hunger to learn as much as possible about development lead him through courses such as DBase III, DBase IV, Pascal, C, C++, Java, and several in UNIX. He started his development career first doing heavy processing with Access and VBA, then moved on to VB 3, Oracle, and Delphi. Visual Basic was one environment that remained constant for many years, including his very first .NET projects performed in Visual Basic.NET.
After working several years on very high end internal Corporate applications, the consultant company he was working for, sought out his ideas for actual software products that could be packaged and sold. He had already developed several prototypes of a dynamic portal application, before portals even became popular, so this became the logic decision and he became the Director of Product Development. Under his direction, a team of developers and graphic artists, took a skinning approach before that become popular, and completed the core portal application, and continued on to developer 15+ add-on modules, including things such as: Help Desk Ticket Systems, Change Control, Records Management, Human Resources, and many more applications. Eventually, it spun off into it's own separate company as KnowledgeGEAR, a complete intranet in the box solution.
Having worked as a consultant, he has had a experience with a very wide range of applications and architectures, at one time, even converting several Fox Pro and GW-Basic applications to VB 6 and ASP. His early training of Unix and the C language and years of experience with JavaScript, lead him very quickly to C#, where he has remained focused ever since.
He is the current President of the
Tulsa Developers .NET user group.. He has been an MCP since 2003 and MCAD and MCSD since 2005. He is currently pursuing his MCDBA and then on to MCSE.