![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 21 to 27 of 27 total |
![]() |
Sat, Mar 4 2006 2:13 AM | Permanent Link |
"Uffe Kousgaard" | "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:580C9D3B-5F25-45F2-9DAC-5F7056C8D2D3@news.elevatesoft.com... > > I'm only going by what Uffe stated he wanted. I didn't "want" anything. I just pointed out that the "problem" could still exist in version 4, which is the current. Yesterday I also discovered a bug in the SQL, that didn't return any records from a complex query. I have solved the problem, by splitting it into 2 queries - an inner join and a where part. But should I report the actual bug? I sure don't know if it is worth it. Regards Uffe |
Sat, Mar 4 2006 3:07 AM | Permanent Link |
Roy Lambert NLH Associates ![]() | Uffe
As Tim says he won't be fixing it for V3 but, just in case its still something that exists in V4 it is worth reporting. Tim's (or another's) answer may even be that its been fixed in V4 in which case it could encourage you to upgrade ![]() Roy Lambert |
Sat, Mar 4 2006 9:42 AM | Permanent Link |
"Uffe Kousgaard" | I have tested with dbsys 4 and the problem is gone there.
"Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message news:4F5F0B7F-BF5F-49F9-90BA-DDF79F67A114@news.elevatesoft.com... > Uffe > > > As Tim says he won't be fixing it for V3 but, just in case its still > something that exists in V4 it is worth reporting. Tim's (or another's) > answer may even be that its been fixed in V4 in which case it could > encourage you to upgrade ![]() > > Roy Lambert > |
Sun, Mar 5 2006 7:25 PM | Permanent Link |
Jeff Cook | "Uffe Kousgaard" <look_at_www.routeware.dk> wrote on Sat, 4 Mar 2006 15:42:05 +0100
>I have tested with dbsys 4 and the problem is gone there. > >"Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message >news:4F5F0B7F-BF5F-49F9-90BA-DDF79F67A114@news.elevatesoft.com... >> Uffe >> >> >> As Tim says he won't be fixing it for V3 but, just in case its still >> something that exists in V4 it is worth reporting. Tim's (or another's) >> answer may even be that its been fixed in V4 in which case it could >> encourage you to upgrade ![]() >> >> Roy Lambert >> > > Uffe So report it for 3.30 + plus the work around that you have discovered. That way everyone who is still using 3.30 (like myself) can get to share your experience! Just don't expect a fix for a mothballed version ![]() Cheers Jeff -- Jeff Cook Aspect Systems Ltd Phone: +64-9-424 5388 Skype: jeffcooknz www.aspect.co.nz |
Mon, Mar 6 2006 5:12 AM | Permanent Link |
"Uffe Kousgaard" | "Jeff Cook" <jeffc@aspect.co.nz> wrote in message
news:91E837B8-D03D-41F0-A481-9AFC0DE2C8F7@news.elevatesoft.com... > > So report it for 3.30 + plus the work around that you have discovered. > That way everyone who is still using 3.30 (like myself) can get to share > your experience! Just don't expect a fix for a mothballed version ![]() > This is how it looked: SELECT table1.id, table2.field1, table3.mydate FROM (table3 INNER JOIN table1 ON table3.id = table1.id) INNER JOIN table2 ON (table1.id = table2.id) AND (table3.mydate=table2.mydate) WHERE (extract(Year from table3.mydate)=2003) and (table2.field1=831) Returned 0 records. Then I removed the part with "table2.field1=831" and now it returned several records, where field1=831 (!) The solution was to run the 2 inner joins first and then apply the whole where clause in a new step. The real problem may be related to field types, index type, specific data values etc. so don't expect to be able to re-create the problem. For instance my ID field is LargeInt. Regards Uffe |
Mon, Mar 6 2006 11:54 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Bill,
<< Firstly, I should apologise for hijacking the thread. I'm actually discussing 4.x but forgot to tell everybody! I've now changed the subject line in this posting. Perhaps I should have started a new thread? >> It doesn't really matter. I did get a little confused, but I doubt if it was anything that you did. ![]() << Secondly, my level of expectation appears to be lower than what you ascribe to Uffe. What I was advocating is that the user interface should reflect the capabilities that exist, rather than that you should enhance the capabilities. After reading what has been said about the situation, I now think the modifications that would fit the bill are:- >> That sounds reasonable. I can put those in with the next minor release/build of 4.x. << I say "was advocating" because I had forgotten how close we are to a release of ElevateDB. Since this is an issue that only affects developers who come across it for the first time, the number affected will presumably dramatically diminish some time "real soon now". 8-) >> Hopefully. ![]() -- Tim Young Elevate Software www.elevatesoft.com |
Mon, Mar 6 2006 11:58 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Uffe,
<< I didn't "want" anything. I just pointed out that the "problem" could still exist in version 4, which is the current. >> My understanding was that you wanted a fix for the "problem". My apologies if that was incorrect. << Yesterday I also discovered a bug in the SQL, that didn't return any records from a complex query. I have solved the problem, by splitting it into 2 queries - an inner join and a where part. But should I report the actual bug? >> Absolutely. Just because I don't agree with you regarding a specific issue is no reason to stop reporting issues or believe that we won't or don't fix problems that are encountered. That simply isn't true, as even yourself can attest to with the amount of time that you've owned DBISAM. -- Tim Young Elevate Software www.elevatesoft.com |
« Previous Page | Page 3 of 3 | |
Jump to Page: 1 2 3 |
This web page was last updated on Wednesday, August 14, 2024 at 03:12 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |