Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB Public Beta Tests » View Thread |
Messages 11 to 16 of 16 total |
IF EXISTS /IF NOT EXISTS |
Tue, Feb 6 2007 9:49 PM | Permanent Link |
Steve Forbes Team Elevate | Hi Ole,
Agree, I would like to see this back too. -- Best regards Steve "Ole Willy Tuv" <owtuv@online.no> wrote in message news:1F8066AB-8B1B-4628-98AC-98880A79A4A6@news.elevatesoft.com... > Tim, > > << But, it certainly didn't allow for testing of the existence of multiple > objects as one condition or anything more complex than the simple > EXISTS/NOT EXISTS test. >> > > IMO, the IF EXISTS clause is a damned good/convenient DDL extension. I > wouldn't be surprised to se this (so far) proprietary extension go into > the SQL standard, since it's a convenient short hand for querying the > metadata - no matter how the system tables are implemented at the vendor > level. > > Ole Willy Tuv > > |
Wed, Feb 7 2007 4:05 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
>To a small degree, yes. However, it's not like DBISAM's scripting was that >rich to begin with. True, you could test for the existence of certain >things. But, it certainly didn't allow for testing of the existence of >multiple objects as one condition or anything more complex than the simple >EXISTS/NOT EXISTS test. Think of the amount of code that saves me as a programmer. Testing for the existence of a table is a bit of code to decide wether to generate some sql or not, but checking for the existence of each field to decide wether to add it into the sql or not is a bit worse, and then when you think what losing REDEFINE does as well its a lot more coding. Roy Lambert |
Wed, Feb 7 2007 12:26 PM | Permanent Link |
"Johnnie Norsworthy" | "Steve Forbes" <ozmosys@spamfreeoptusnet.com.au> wrote in message
news:7E8878BC-9281-4496-A7DF-EB777B400DD7@news.elevatesoft.com... > Hi Ole, > > Agree, I would like to see this back too. I use it also. -Johnnie |
Wed, Feb 7 2007 4:56 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< Think of the amount of code that saves me as a programmer. Testing for the existence of a table is a bit of code to decide wether to generate some sql or not, but checking for the existence of each field to decide wether to add it into the sql or not is a bit worse, and then when you think what losing REDEFINE does as well its a lot more coding. >> I understand that is saves code. To reiterate, EDB was written to the SQL standard as much as humanly possible *to start with*. After the initial release, we will begin to review what can be added and/or extended. This is not the time for me to be adding new features. The feature set is set for at least the next 2 months as we roll out the rest of the EDB line of products. REDEFINE was a bit of a hack. The DROP and ADD in the same statement is much cleaner without losing any of the benefits. -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Feb 8 2007 4:15 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
>The feature set is set for >at least the next 2 months as we roll out the rest of the EDB line of >products. Does that mean I only have a 2 months and 1 day wait Roy Lambert |
Thu, Feb 8 2007 1:17 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< Does that mean I only have a 2 months and 1 day wait >> Something like that, yes. -- Tim Young Elevate Software www.elevatesoft.com |
« Previous Page | Page 2 of 2 | |
Jump to Page: 1 2 |
This web page was last updated on Saturday, May 4, 2024 at 12:54 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |