Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 6 of 6 total |
COMPUTED column |
Tue, Feb 12 2008 2:26 PM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Is there a way to do a lookup into another table eg
SELECT _Name FROM Career JOIN Companies C ON C._ID = _fkCompanies If so can you give me an example of the syntax. Ta Roy Lambert |
Tue, Feb 12 2008 2:51 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< Is there a way to do a lookup into another table eg >> Not currently, no. I didn't want to introduce any unwieldly dependencies in the computed columns initially until I had some time to think through the ramifications. -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Feb 13 2008 2:23 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
I can think of lots of ramifications a bit like RI but worse cos its "hidden". I also don't know what it would do to performance (that's what I was hoping to test) Roy Lambert |
Wed, Feb 13 2008 5:15 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< I can think of lots of ramifications a bit like RI but worse cos its "hidden". I also don't know what it would do to performance (that's what I was hoping to test) >> Performance would actually be quite good. However, the issue that I forgot about was that sensitive result sets use computed columns for implementing "live expressions", and the requirement is that the computed columns only allow expressions that can be re-computed client-side with remote sessions using the existing information in the same row. Otherwise, any modifications to other columns in the same row would require a round-trip to the server (or more), thus resulting in fairly poor performance. -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Feb 13 2008 5:37 PM | Permanent Link |
Fernando Dias Team Elevate | Tim
> Performance would actually be quite good. However, the issue that I forgot > about was that sensitive result sets use computed columns for implementing > "live expressions", and the requirement is that the computed columns only > allow expressions that can be re-computed client-side with remote sessions Is this issue also related with the sub-queries suggestion I posted 2 days ago, or are they completely different things? -- Fernando Dias Easygate, Lda |
Fri, Feb 15 2008 6:13 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Fernando,
<< Is this issue also related with the sub-queries suggestion I posted 2 days ago, or are they completely different things? >> Actually, that's 100% correct, and something that I really need to think about further. I think I can solve it by using generated columns instead for the sub-query values. That way they will stay static and stored in the row on the client-side. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Saturday, April 27, 2024 at 08:52 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |