smarthaert / txquery

Automatically exported from code.google.com/p/txquery
Other
0 stars 0 forks source link

Null value in source field causes incorrect & unexpected results on rare occasions #44

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Hi,

I have been trying to track down this problem for weeks, and believe I finally 
have a way of replicating this issue for demonstration.

I have been experiencing on the vary rare occasion results from TxQuery that 
have not grouped / combined matching records together, where the result gives a 
separate record for every record in the source dataset.

It appears as though the problem has to do with null values in one of the 
fields. This problem does not happen with all result sets, and strangely enough 
- if I add an additional record to the existing result set, the problem 
dissapears (hence it being very difficult to replicate).

However, I have now been able to create a demo application that will show both 
the problem, as well as what the expected result should be (attached).

Steps to replicate:

1) Extract the attached demo project, along with the table (xquery.dbf) to a 
destination

2) Open the project, and change the path of the TicketQAQ.DatabaseName to the 
location of the extracted files. 

3) Run the project. If you click on the RUN USING BDE button, you will see a 
result set with many records - where it does not group as expected.

4) Click on the Remove Contract from XQUERY button, and then the RUN USING BDE 
again - and the resultset will be only 3 records - as I expect it to be.

This problem occurs not only with the BDE, but also with another database 
(DBISAM). It took me some time to be able to replicate the issue using the BDE 
to submit an example project.

This problem is currently plaguing my software, so I'm excited to finally 
hopefully finding a solution. Any help will be greatly appreciated!

I am using Delphi 2007 just incase this is isolated to pre-XE software.

Best Regards

Adam.

Original issue reported on code.google.com by wsdah...@gmail.com on 18 Jun 2013 at 11:45

Attachments:

GoogleCodeExporter commented 9 years ago
Hi what version are you sing, try the one I uploaded at : 
http://code.google.com/p/txquery/issues/detail?id=40

I have fixed D2007 compilation.

Original comment by fdue...@gmail.com on 22 Jul 2013 at 5:58

GoogleCodeExporter commented 9 years ago
Hi please check the latest version posted in this issue:
http://code.google.com/p/txquery/issues/detail?id=40

Original comment by fdue...@gmail.com on 23 Jul 2013 at 9:24

GoogleCodeExporter commented 9 years ago
HI please check latest release of TxQuery 3.01

Original comment by fdue...@gmail.com on 1 Aug 2013 at 6:00

GoogleCodeExporter commented 9 years ago
Hi,

Sorry for the delay. I have been on annual leave.

I have just compiled TxQuery 3.01 into D2007 and the problem still occurs with 
the latest release.

Sorry for the bad news...

Original comment by wsdah...@gmail.com on 26 Aug 2013 at 11:20

GoogleCodeExporter commented 9 years ago
Unfortunately this issue still remains - just looking for any suggestions 
please?

Original comment by wsdah...@gmail.com on 18 Feb 2015 at 5:31