Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB SQL » View Thread |
Messages 1 to 3 of 3 total |
v1 -> v2 memory table problem |
Mon, Sep 14 2009 4:27 PM | Permanent Link |
Michael Fullerton | After upgrading from EDB 1 to EDB2 my app gives an error #700 on
running a particular query: The table or view MyTable does not exist. The problem sql uses a join between a memory table and a regular table. SELECT MT.Field1, T.Field2 FROM MEMORY.MyMemoryTable MT JOIN MyTable T ON(MT.ID=T.ID) Has anything changed in v2 in this respect? I don't see anything in the release notes. |
Mon, Sep 14 2009 9:25 PM | Permanent Link |
Michael Fullerton | On Mon, 14 Sep 2009 13:27:33 -0700, Michael Fullerton
<fullerm@cybermatrix.com> wrote: >After upgrading from EDB 1 to EDB2 my app gives an error #700 on >running a particular query: > >The table or view MyTable does not exist. > >The problem sql uses a join between a memory table and a regular >table. > >SELECT MT.Field1, T.Field2 FROM MEMORY.MyMemoryTable MT JOIN MyTable T >ON(MT.ID=T.ID) > >Has anything changed in v2 in this respect? I don't see anything in >the release notes. OK I understand the problem. The non-memory table needs to have its database name in front of it too. Why is that? Can this be changed? |
Mon, Sep 14 2009 11:25 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Michael,
<< OK I understand the problem. The non-memory table needs to have its database name in front of it too. Why is that? Can this be changed? >> It's a bug in 2.02 B15. It will be fixed in the 2.03 release. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Sunday, May 19, 2024 at 08:46 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |