Visokio website     Downloads     Video tutorials     KnowledgeBase  
DataManager: Database import block SQL error? - Visokio Forums
DataManager: Database import block SQL error?
  •     bfromson1 December 18, 2012 7:05AM
    I tried to set up filters in a database import block for a text field "does not contain" a text string.

    1) The query returned no records, as the SQL generated was looking for it to contain the text.

    2) And while clicking between the "Configuration" "Filters" and "View SQL" tabs it has lost my field selections and gone back to select all

    3) Minor UI issue, if you expand the View SQL box horizontally the text wrap extends out so that the SQL string extends across the available view. If you then make the view smaller horizontally it doesn't re-wrap the text but puts a scroll bar on the horizontal axis of box - minor problem, but what's wrong with perfection!
    omnisqlbug.docx 183K
  •     bfromson1 December 18, 2012 7:06AM
    Forgot to add --- 2.8 b 443
  •     chris December 18, 2012 8:52AM
    Hi - Thanks for the comments and the kind words at the end :)

    1. I don't fully understand what you mean here. If you are looking for an empty text field you should use "has no value".

    2. This is a bug. We will investigate and fix it ASAP.

    3. Thanks for notifying us of this UI issue.

  •     bfromson1 December 18, 2012 9:54AM
    I was looking for records from a datatable where the account status did not include the word client.

    On filters tab select the field "Account Status"
    select the operator "does not contain"
    enter text "client" in the text box.

    The matching SQL snippet should have stated:

    where [AccountStatus] NOT LIKE '%client%'

    instead it has the snippet

    where [AccounStatus] LIKE 'client'

    and so the query failed

    The attached word file has the screenshots of the filter and SQL tabs.
  •     bfromson1 December 21, 2012 4:28AM
    Chris - any progress on point 1.

  •     chris December 21, 2012 4:31AM
    Hi Bernard,

    We are investigating your issues, and hope to have them fixed soon. In the meantime you could create a custom SQL statement to retrieve your data.
  •     chris December 21, 2012 10:15AM
    Hi. We have now fixed issues 1. and 2. This fix will be in the next Omniscope 2.8 release.


It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Apply for Membership