Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB Public Beta Tests » View Thread |
Messages 1 to 10 of 11 total |
Should this syntax still work? |
Tue, Feb 27 2007 12:13 PM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
I get an error 700 with the syntax below. update techniquesdocs T set _onDisk = True from techniquesdocs T join diskdocs D on T._Path = D._Path Assuming its not a bug what's the correct syntax anyone. Roy Lambert |
Wed, Feb 28 2007 8:57 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< I get an error 700 with the syntax below. update techniquesdocs T set _onDisk = True from techniquesdocs T join diskdocs D on T._Path = D._Path Assuming its not a bug what's the correct syntax anyone. >> A correlated sub-query will do what you want: update techniquesdocs T set _onDisk = True where T.Path=(SELECT D.Path FROM diskdocs D WHERE D._Path=T._Path) -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Feb 28 2007 10:22 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
After many years ignoring it I started to learn SQL. I was getting to understand it and now I have to learn that gibberish. Wow talk about non-intuitive. When I win the lottery I'm taking out a contract on everyone involved in setting up the sql standard. Rant over and thanks Tim Roy Lambert |
Wed, Feb 28 2007 11:24 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | ps
Can we have examples of this sort of thing in the manual, or please recommend a good book Roy Lambert |
Wed, Feb 28 2007 11:59 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< Can we have examples of this sort of thing in the manual, or please recommend a good book >> I'll see about adding it as an example. -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Feb 28 2007 11:59 AM | Permanent Link |
"Donat Hebert \(Worldsoft\)" | Does that mean we've lost the ability to update a bunch of columns at the
same time? ie I've used the correlated sub-query in other implementations but just hated it when I had to update more than one column. We have instances where we update many columns from the joined table. Thx. > A correlated sub-query will do what you want: > > update techniquesdocs T set _onDisk = True > where T.Path=(SELECT D.Path FROM diskdocs D WHERE D._Path=T._Path) > > -- > Tim Young > Elevate Software > www.elevatesoft.com > > > |
Thu, Mar 1 2007 5:09 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Donat,
<< Does that mean we've lost the ability to update a bunch of columns at the same time? >> No, you just have to use a correlated sub-query for each column. -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Mar 1 2007 10:41 AM | Permanent Link |
"Donat Hebert \(Worldsoft\)" | Ok, I see how that works but that will multiply processing time by n times
columns. (not counting the less than appealing syntax with complex joins) That's really unfortunate. Your implementation on DBISAM is a real pleasure to work with. Donat. "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message news:24EF9541-430C-46CF-B37E-4DF43F40B13C@news.elevatesoft.com... > Donat, > > << Does that mean we've lost the ability to update a bunch of columns at > the same time? >> > > No, you just have to use a correlated sub-query for each column. > > -- > Tim Young > Elevate Software > www.elevatesoft.com > |
Fri, Mar 2 2007 7:34 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Donat,
<< Ok, I see how that works but that will multiply processing time by n times columns. (not counting the less than appealing syntax with complex joins) That's really unfortunate. Your implementation on DBISAM is a real pleasure to work with. >> I don't like the additional FROM syntax and didn't want to make a rush decision, which is why it was left out. However, it is the same as with SQL Server, so I may end sticking with it for compatibility reasons. -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Mar 8 2007 11:33 AM | Permanent Link |
"Ole Willy Tuv" | Tim,
<< I don't like the additional FROM syntax and didn't want to make a rush decision, which is why it was left out. However, it is the same as with SQL Server, so I may end sticking with it for compatibility reasons. >> As an alternative, have you considered multiple column assignment ? Example: update table1 t1 set (col1, col2, col3) = ( select col1, col2, col3 from table2 t2 where t2.col1 = t1.col1 ) Ole Willy Tuv |
Page 1 of 2 | Next Page » | |
Jump to Page: 1 2 |
This web page was last updated on Tuesday, April 30, 2024 at 03:55 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |