This never occurred to me to try, but today, trying to solve a problem, I ran a SQL statement that attempted to use the UPDATE clause on an in-memory table. Much to my surprise (and delight), this worked! I had no idea that you could do this. To test it even further, I ran a DELETE clause as well. Worked like a charm!
Here is a demo of this in action:
- <cfquery name="qID" datasource="#REQUEST.DSN.Source#">
- @id TABLE (
- id1 INT,
- id2 INT
- Populate the in-memory table variable with the
- pivot data. We are going to store the same ID
- into both columns so that we can demonstrate
- that it was updated.
- INSERT INTO @id
- SELECT TOP 5
- p.id AS id1,
- p.id AS id2
- pivot100 p
- <!--- Update the in-memory query. --->
- id2 = (id2 + 5)
- <!--- Delete from the in-memory query. --->
- DELETE FROM
- id1 >= 4
- <!--- Select all values from the in-memory table. --->
- <!--- Dump out the query with both ID columns. --->
- label="ID Query"
CFDumping out the returned ColdFusion query object, we get:
| || || |
| || |
| || || |
Notice that the UPDATE added 5 to the id2 column and that the DELETE deleted the last two records. I can't believe I am only learning this now!
Looking For A New Job?
- Sr. Cold Fusion Web Developer at Vemma Nutrition
- Senior .NET Software Developer with API Experience at Marketing Holdings
- ColdFusion & AngularJS Web Developer for rapidly growing startup - at Intuvo
- Senior Coldfusion Web Developer (UK - Kent) at EPG Health Media
- Web Developer at Bridge Catalog
Trying to do it in a Query of Query is not so simple though! (but doable)
Very true! If ColdFusion could come up with a way to support UPDATE and DELETE in query of queries... I don't know what I would do, but it would be nuts!
Thanks for posting this. I always enjoy reading your blog since I always learn something.
I've never thought about using in-memory sql tables. What would be some good reasons to use them?
In-memory tables are great for when you need to do some sort of intermediary data filtering before your primary query. For instance, you might create a table variable that holds just a column of "valid" IDs for a table. Then you could join that to another table:
u.id = vu.id
Assuming that @valid_user is a table object that has only valid IDs, this INNER JOIN would force only users with IDs in that valid_user table to be returned.
Not the best example, but I promise in-memory tables are awesome :)
Thank you for this. I have never used temp tables before because I usually did most database work through datasets. This could be very useful.
One question. is this supported with this syntax in both MSSQL and mySQL?
Thanks for this and your articles on CSV Parsing in particular. They have been very helpful with a project I am doing at home during the time I should be sleeping.
Glad to help. I am not sure about mySQL as I work in MS SQL Server 99% of the time. I assume that this stuff is mostly standard, but I that is just a guess. I know mySQL had a lot of "annoying" features in earlier versions that have been cleaned up in the latest release (or so I have been told) so hopefully this should work in the newest version.
It's probably worth noting that table variables (@temp) in MS SQL are stored in RAM, as opposed to regular temp tables (#temp) are stored in the tempdb and require disk I/O. I use table variables when handling under 3000 records or so. Any larger and SQL Server will automatically start swapping data in the table to disk and the performance benifit is lost. Also I believe you can place indexes on a temp table, but not a table variable.
Another random fact. SQL Server 2005 will let you insert into a table variable with the output of a stored proc:
INSERT INTO @tmp
In SQL server 2000 you could only do this with temp tables.