2009-09-30 22:45:18 UTC
Hi pmallegrom,
I had this same issue a couple of years ago. At the time, we determined that the problem was caused by the fact that MSSQL (the database I was working with at the time) didn't expose information about the defaults for procedure parameters.
I wound up writing an add-in to MyGeneration, that parsed the full text of the stored procedure, to pull out the default values and populate them into the User MetaData. I then used those custom metadata fields for my scripts.
Unfortunately, I have had a hard-drive crash and have lost all of that work. I am unable to locate the original source for that add-in.
That is why I'm here actually... To find out if the problem had ever been resolved in the official release. Upon examining the MetaData from v1.3, I can see that this problem still exists.
I really hate doing work twice, so I'm going to spend some more time, trying to find out if I can locate the original source for my plug-in. It wasn't elegant, but it worked.
If I can't find it, I suspect I am going to have to do the work all over again.
