why have drop procedures been removed from the codesmith templates for SPs?

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
This thread is closed to new posts. You must sign in to post in the forums.
2/21/2012 2:07:43 AM
Gravatar
Total Posts 192

why have drop procedures been removed from the codesmith templates for SPs?

hi Joe.

the older codesmith templates generated some scripts at the start that first removed the stored procedures if they already existed.

what has happened to them?

(though, the one that was right before the procedure for paging is still generated)

(using mssql)

2/21/2012 8:03:41 AM
Gravatar
Total Posts 18439

Re: why have drop procedures been removed from the codesmith templates for SPs?

nothing has been removed recently. I never used those, I copy paste only what I need for those generated results. Syntax for checking if something exists varies across sql versions and can be subject ot permission errors and makes installation scripts more difficult to maintain. Furthermore if you are using the installation system there should never be a reason to drop something just to create or alter it since you know whether it already exists in a previous install script or not. So it just isn't needed. If you need it feel free to modify your own version of the codesmith templates.

These codesmith templates are what I use, I share them but I don't say they are a complete or perfect solution for every need. You are free to copy them and modify as you wish to make them better suited for your own preferences. I use them only to save some typing, I often modify the generated code.

2/21/2012 8:17:13 AM
Gravatar
Total Posts 192

Re: why have drop procedures been removed from the codesmith templates for SPs?

OK.

I'm just trying to be a helping and active community member and inform you if anything ever happens that you may not be aware of it.

I'd thought you removed the ones which where at the top of mp_MSSQLStoredProcedureGenerator.cst and forgot the one which is somewhere in the middle of the file, but I now see that the template hasn't changed and the generator is just not doing what it used to do (for any reason).

forget it.

2/21/2012 8:23:43 AM
Gravatar
Total Posts 18439

Re: why have drop procedures been removed from the codesmith templates for SPs?

I'm sure I did delete them from the top but it was a long time ago. If I missed the one at the bottom it was an oversight. I don't use those drop statements. I know you are trying to be helpful.

Best,

Joe

You must sign in to post in the forums. This thread is closed to new posts.