Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Enhancement Requests and Suggestions » View Thread |
Messages 1 to 6 of 6 total |
stored procedure versions |
Fri, Jul 25 2008 11:05 PM | Permanent Link |
"David Cornelius" | It's nice having table versions--I can send a script to my customer and
have it automatically check the table version to see if it matches the latest version and update it if not. I've just run into a situation where I need to update a customer's stored procedure. Sure, I can always call ALTER PROCEDURE, but it suddenly dawned on me that stored procedures don't have versions. I hadn't really thought about this before, but they might need to be modified once in a while as well. OK, I could check the version of one of the tables it uses and update the version of that table, I suppose. But then I introduce a non-necessary table update (although that wouldn't hurt anything). An interesting thought though--is there a way to give stored procedures version numbers like the tables have? I suppose we could extend that idea to functions and views as well! -- David Cornelius CorneliusConcepts.com |
Sat, Jul 26 2008 4:35 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | David
As a workround you could put a comment into the SP with a version number. On those probably rare occasions when you need to check load into a component and parse the SQL. Roy Lambert |
Sun, Jul 27 2008 2:18 PM | Permanent Link |
"David Cornelius" | > As a workround you could put a comment into the SP with a version
> number. On those probably rare occasions when you need to check load > into a component and parse the SQL. This is done totally with SQL. At application startup, I use a script to load a SQL file that is shipped with the update and run it as the first thing the app does. Parsing out a comment in the current database's stored procedure is impractical. -- David Cornelius CorneliusConcepts.com |
Mon, Jul 28 2008 2:48 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | David
OK, I can see that would be awkward. You could use the description column. Should be possible to interrogate that as part of your update procedure. Roy Lambert |
Mon, Jul 28 2008 3:45 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | David,
<< An interesting thought though--is there a way to give stored procedures version numbers like the tables have? I suppose we could extend that idea to functions and views as well! >> Very good idea. I'll put it on the list for 2.02. -- Tim Young Elevate Software www.elevatesoft.com |
Mon, Jul 28 2008 7:10 PM | Permanent Link |
"David Cornelius" | > Very good idea. I'll put it on the list for 2.02.
Awesome! Thanks. -- David Cornelius CorneliusConcepts.com |
This web page was last updated on Wednesday, April 24, 2024 at 11:07 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |