Possible query bug in dbase driver

  • I have come accross a bug while doing command line queries on an image level that only happens when using the dbase driver and version 1412 onwards. My testing is on the linux version but I think it will be the same for windows.


    The command ./dgate --query:"DICOMImages|SOPInstanc, ObjectFile|SeriesInst='1.3.46.670589.28.1.1.2198218821.482595673699.3'|%s %s" on my database should return 4 records.


    Mysql or postgres on all versions of conquest returns the expected 4 records.
    Dbase on version 412alpha or earlier returns the expected 4 records.
    Dbase on version 412 or later ignors the filter and returns all images in the database.


    What is even more curious is that looking up the same records with the cgi interface works correctly in all versions, but if you run exactly the same command externally it has the same behaviour as mentioned above.

  • The problem is that there need to be spaces are the = in the query for dbase. This is indeed new in 1.4.12 and will remain that way as the simple dbaseiii sql parser needs the spaces:


    ./dgate --query:"DICOMImages|SOPInstanc, ObjectFile|SeriesInst = '1.3.46.670589.28.1.1.2198218821.482595673699.3'|%s %s"


    works correctly. The dbase driver is not a full sql server.


    Marcel

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!