Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 10 of 13 total |
Renaming fields |
Sat, Mar 10 2007 8:16 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
When you get round to building support for this in will it also go through everything in the catalog and alter the names eg Indices, Triggers? Roy Lambert |
Mon, Mar 12 2007 4:54 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< When you get round to building support for this in will it also go through everything in the catalog and alter the names eg Indices, Triggers? >> Just direct references to the columns in constraints, indexes or trigger columns, not the actual trigger routines themselves. -- Tim Young Elevate Software www.elevatesoft.com |
Tue, Mar 13 2007 3:55 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
><< When you get round to building support for this in will it also go >through everything in the catalog and alter the names eg Indices, Triggers? > >> > >Just direct references to the columns in constraints, indexes or trigger >columns, not the actual trigger routines themselves. So the consequence is any time you rename a field you have to 1)unload triggers, procedures and functions 2)rename the column 3)edit the triggers, procedures and functions and then reload them? Ouch. Roy Lambert |
Tue, Mar 13 2007 6:18 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< So the consequence is any time you rename a field you have to 1)unload triggers, procedures and functions 2)rename the column 3)edit the triggers, procedures and functions and then reload them? >> Yes, that would be the process. Compiling the SQL in the triggers, procedures, or functions may require resolving items that are only resolvable at runtime (think DDL or temporary tables), therefore it isn't possible for us to cascade the changes in a lot of cases. -- Tim Young Elevate Software www.elevatesoft.com |
Tue, Mar 13 2007 6:19 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< So the consequence is any time you rename a field you have to 1)unload triggers, procedures and functions 2)rename the column 3)edit the triggers, procedures and functions and then reload them? >> BTW, this is no different than any other type of dynamic SQL that references columns that have been renamed, and the triggers, procedures, and functions are essentially dynamic SQL in EDB. Trust me when I say that you'd rather have the dynamic SQL over the statically-bound SQL in terms of flexibility and ease-of-use. -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Mar 14 2007 4:25 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
>BTW, this is no different than any other type of dynamic SQL that references >columns that have been renamed, and the triggers, procedures, and functions >are essentially dynamic SQL in EDB. Trust me when I say that you'd rather >have the dynamic SQL over the statically-bound SQL in terms of flexibility >and ease-of-use. 1) I don't care about anyone else's flavour of dynamic sql 2) Were you ever a used car salesman? Roy Lambert ps it seems like ElevateDB is getting like electronics in modern cars. Mine has been in the garage 4 weeks now. Every time the computer diagnoses a fault it gets fixed but then there's another one. Its all to pervasive and interlinked. Bring back side valve engines! pps A lot of the delay is caused by getting the parts - I live at the arse end of nowhere |
Wed, Mar 14 2007 6:19 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< ps it seems like ElevateDB is getting like electronics in modern cars. Mine has been in the garage 4 weeks now. Every time the computer diagnoses a fault it gets fixed but then there's another one. Its all to pervasive and interlinked. Bring back side valve engines! >> I don't understand the analogy - the issue that you're complaining about is that EDB *doesn't* automatic update links and references to column names in SQL in triggers and stored procedures/functions. In fact, such an issue with column names is only an issue until the stored procedure or trigger is actually compiled and EDB attempts to execute it. IOW, if you never compile and execute the SQL that references the column name in question, then there would never be an issue. This also allows you to drop and move around column names without touching the stored procedures, triggers, etc. as long as the column names end up staying the same. This is not the case with other databases where the column names are bound to the stored procedure or trigger via the catalog. -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Mar 15 2007 4:21 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
Possibly a poor analogy brought on by the frustration of not having a car Roy Lambert |
Fri, Mar 16 2007 3:58 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< Possibly a poor analogy brought on by the frustration of not having a car >> Aren't you kind of out in the country also ? -- Tim Young Elevate Software www.elevatesoft.com |
Sat, Mar 17 2007 6:55 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
Yup. A nice little village. But the nearest garage is c15 miles away. Roy Lambert |
Page 1 of 2 | Next Page » | |
Jump to Page: 1 2 |
This web page was last updated on Thursday, May 23, 2024 at 03:39 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |