June 21, 2012 at 9:47 am
I absolutely agree with you that this should never be used in production and was certainly not attempting to defend that position.
Just saying that as a generation tool it has some potential merit in certain use cases though I'll admit I didn't explicitly state that I merely intended it for use as a generation tool.
June 21, 2012 at 9:52 am
JeffRush (6/21/2012)
You are tasked with pulling out the data across 50 tables. They all contain any number of columns. You want all of it but know for a fact you don't want CreatedDate, CreatedByUserID, UpdatedDate, UpdatedByUserID, as an example.An edge case certainly but generating it via that code would be more effective than manually commenting it out for 50 tables.
Have to agree with Jared. Writing to code to generate code on the fly and run it makes the application more difficult to maintain than it probably needs. I have written numerous routines to generate code, but it was one time generation, not everytime a procedure was run.
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply