Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: SVN trunk
    • Fix Version/s: SVN trunk
    • Component/s: framework
    • Labels:
      None

      Description

      This is a new feature to manage SQL queries.
      You can :

      • store/update/delete SQL query
      • store/update/delete parameters for this query
      • execute query and view results into worksheet

      This SQL query manager is usefull to run frequently queries (ie: for maintenance report)

      How to use it :

      • goes to webtools/Entity Engine Tools
      • select "SQL queries library" item
      • create a new query and fill in SQL. If you want to use parameters, add them like this : select * from facility where facility_Id = '$ {facilityId}

        '

      • to declare parameters for this query then goes to "Add or update query parameter" screenlet and fill in fields : description = facility id ; Parameter = facilityId
      • to execute SQl query then press buton "run"
      • fill in parameters value adn press buton "run"
      • worksheet should automaticaly open

        Activity

        Hide
        Gaudin Pierre added a comment -

        The patch to apply on OFBiz-trunck

        Show
        Gaudin Pierre added a comment - The patch to apply on OFBiz-trunck
        Hide
        Erwan de FERRIERES added a comment -

        Hi Pierre,
        I took a quick look at your patch. It seems there are some formatting issues (tabs maybe ?), and you leaved the @author tag. Could you update it ?

        Regards,

        Show
        Erwan de FERRIERES added a comment - Hi Pierre, I took a quick look at your patch. It seems there are some formatting issues (tabs maybe ?), and you leaved the @author tag. Could you update it ? Regards,
        Hide
        Gaudin Pierre added a comment -

        Hi Erwan,

        Thank you very mutch for this "quick look".

        Could you please attach to JIRA screenshots about formating issues ?

        I'll update @author tag and send you a new patch.

        Best regards

        Pierre

        Show
        Gaudin Pierre added a comment - Hi Erwan, Thank you very mutch for this "quick look". Could you please attach to JIRA screenshots about formating issues ? I'll update @author tag and send you a new patch. Best regards Pierre
        Hide
        Erwan de FERRIERES added a comment -

        hi Pierre,
        not speaking about UI, but code formatting.

        Cheers,

        Show
        Erwan de FERRIERES added a comment - hi Pierre, not speaking about UI, but code formatting. Cheers,
        Hide
        Erwan de FERRIERES added a comment -

        Hi Pierre,

        any progress ?

        Cheers,

        Show
        Erwan de FERRIERES added a comment - Hi Pierre, any progress ? Cheers,
        Hide
        Markus M. May added a comment -

        Hi, I found this issue kind of interesting. The patch is already in my local working branch and seems to be working (well, mostly). Unfortunately there seems to be a dependency added from webtools to the application/content, because of an entity defined in there needed for the webtools.

        Question is now, how to approach something like this correctly. IMHO it is a no-go to reference the application/content from the webtools. Should this tool be packed into its own component then?

        Show
        Markus M. May added a comment - Hi, I found this issue kind of interesting. The patch is already in my local working branch and seems to be working (well, mostly). Unfortunately there seems to be a dependency added from webtools to the application/content, because of an entity defined in there needed for the webtools. Question is now, how to approach something like this correctly. IMHO it is a no-go to reference the application/content from the webtools. Should this tool be packed into its own component then?
        Hide
        Adrian Crum added a comment -

        If we wanted to implement something like this, then it would be best to use the SQL parsing code found in the entity engine. The SQL parser converts SQL to Entity Expressions and then uses the Entity Engine to execute the SQL. That approach maintains database compatibility.

        Show
        Adrian Crum added a comment - If we wanted to implement something like this, then it would be best to use the SQL parsing code found in the entity engine. The SQL parser converts SQL to Entity Expressions and then uses the Entity Engine to execute the SQL. That approach maintains database compatibility.
        Hide
        Markus M. May added a comment -

        Ah, sure.

        The patch references application/content because the results are transformed to XLS, and therefor it needs the POI dependencies found in the application/content component.

        Guess this whole thing is not really what I wanted. Anyway, thanks for your input.

        Show
        Markus M. May added a comment - Ah, sure. The patch references application/content because the results are transformed to XLS, and therefor it needs the POI dependencies found in the application/content component. Guess this whole thing is not really what I wanted. Anyway, thanks for your input.

          People

          • Assignee:
            Erwan de FERRIERES
            Reporter:
            Gaudin Pierre
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development