Uploaded image for project: 'i2b2 Web Client'
  1. i2b2 Web Client
  2. WEBCLIENT-290

Unable to rename a query in Previous Queries section

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.7.11
    • None
    • None
    • Previous Queries
    • PostgreSQL
    • Firefox

    Description

      Steps to reproduce issue:
      1. Log into i2b2 webclient with access to at least project.
      2. Navigate to Previous Queries section (there should be at least one previously run query listed)
      3. Right click the previously run query and click rename
      4. Enter a different name for the query when prompted and hit OK.

      Expected result: The new query name should be saved and displayed in the Previous Queries section upon submitting.

      Observed result: Nothing happens. The old query name still shows up in the Previous Queries section. There is no error message thrown in UI or in server log. The new query name is not saved in the database and is basically lost. This feature worked fine in i2b2 v1.7.06 but not in v1.7.07.

      Attachments

        Activity

          nich Nich added a comment - - edited
          I am unable to reproduce this issue. Does it still occur for you, Snehil?

          Thanks,
          Nich
          nich Nich added a comment - - edited I am unable to reproduce this issue. Does it still occur for you, Snehil? Thanks, Nich
          sguptawustl Snehil Gupta added a comment - - edited
          @Nich, this issue still occurs in our i2b2 instance. We are now on v1.7.07c. I could probably demonstrate the issue through a web meeting if it helps. Please let me know.
          sguptawustl Snehil Gupta added a comment - - edited @Nich, this issue still occurs in our i2b2 instance. We are now on v1.7.07c. I could probably demonstrate the issue through a web meeting if it helps. Please let me know.
          nich Nich added a comment -
          Hi Snehil,

          I tried this at http://www.i2b2.org/webclient where it is running 1.7.08b, and cannot reproduce the issue. When you turn in debug mode in the web client (to view the XML message logs), does the renameQueryMaster XML response show <condition type="DONE">DONE</condition>?

          Thanks,
          Nich
          nich Nich added a comment - Hi Snehil, I tried this at http://www.i2b2.org/webclient where it is running 1.7.08b, and cannot reproduce the issue. When you turn in debug mode in the web client (to view the XML message logs), does the renameQueryMaster XML response show <condition type="DONE">DONE</condition>? Thanks, Nich
          sguptawustl Snehil Gupta added a comment -
          Hi Nich,

          I enabled the debug mode and found the following error in XML message log while trying to rename a query:

          <condition type="ERROR">PreparedStatementCallback; bad SQL grammar [update i2b2demodata.qt_query_master set name = ? where query_master_id = ? and delete_flag = ?]; nested exception is org.postgresql.util.PSQLException: ERROR: operator does not exist: integer = character varying
            Hint: No operator matches the given name and argument type(s). You might need to add explicit type casts.
            Position: 73</condition>

          Please let me know if you need more information.
          sguptawustl Snehil Gupta added a comment - Hi Nich, I enabled the debug mode and found the following error in XML message log while trying to rename a query: <condition type="ERROR">PreparedStatementCallback; bad SQL grammar [update i2b2demodata.qt_query_master set name = ? where query_master_id = ? and delete_flag = ?]; nested exception is org.postgresql.util.PSQLException: ERROR: operator does not exist: integer = character varying   Hint: No operator matches the given name and argument type(s). You might need to add explicit type casts.   Position: 73</condition> Please let me know if you need more information.
          Hi Nich, any updates on this issue. Please note, our i2b2 instance is hosted in Postgres 9.5. Please see i2b2demodata.qt_query_master table DDL below:

          CREATE TABLE i2b2demodata.qt_query_master
          (
            query_master_id serial NOT NULL,
            name character varying(250) NOT NULL,
            user_id character varying(50) NOT NULL,
            group_id character varying(50) NOT NULL,
            master_type_cd character varying(2000),
            plugin_id integer,
            create_date timestamp without time zone NOT NULL,
            delete_date timestamp without time zone,
            delete_flag character varying(3),
            request_xml text,
            generated_sql text,
            i2b2_request_xml text,
            pm_xml text,
            CONSTRAINT qt_query_master_pkey PRIMARY KEY (query_master_id)
          )
          WITH (
            OIDS=FALSE
          );

          Doesn't look like there is any data type mismatch. Please let me know how to resolve this error.
          sguptawustl Snehil Gupta added a comment - Hi Nich, any updates on this issue. Please note, our i2b2 instance is hosted in Postgres 9.5. Please see i2b2demodata.qt_query_master table DDL below: CREATE TABLE i2b2demodata.qt_query_master (   query_master_id serial NOT NULL,   name character varying(250) NOT NULL,   user_id character varying(50) NOT NULL,   group_id character varying(50) NOT NULL,   master_type_cd character varying(2000),   plugin_id integer,   create_date timestamp without time zone NOT NULL,   delete_date timestamp without time zone,   delete_flag character varying(3),   request_xml text,   generated_sql text,   i2b2_request_xml text,   pm_xml text,   CONSTRAINT qt_query_master_pkey PRIMARY KEY (query_master_id) ) WITH (   OIDS=FALSE ); Doesn't look like there is any data type mismatch. Please let me know how to resolve this error.
          This is reproducible in i2b2 v1.7.08b in PostgreSQL environment.
          sguptawustl Snehil Gupta added a comment - This is reproducible in i2b2 v1.7.08b in PostgreSQL environment.

          People

            mem61 Mike Mendis
            sguptawustl Snehil Gupta
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: