1 4 5 6 7 8 Previous Next 201 Replies Latest reply: Oct 30, 2007 11:38 AM by 478676 Go to original post RSS
      • 75. Re: APEX 3.1 Enhancements
        455564
        A couple of requests that have recently caused issues:

        1) Improved impact analysis across applications and applications in a worksheet. For example, where is a table/column used in an application.

        2) Gantt charts to be added as one of the available Flash charts.

        3) Tabular forms improvements to include the availability of Pop-Up lists, plus improvements to ensure don't overload lists with too many possible values for large searches.
        • 76. Re: APEX 3.1 Enhancements
          Phil UK
          ability to use bind variables when creating a collection from an SQL query
          • 77. Re: APEX 3.1 Enhancements
            Denes Kubicek
            Phil,

            There is a way to do that using the following procedure, prior to parsing your SQL to
            the apex_collection.create_collection_from_query. Based on this code, you may create
            your own package / procedure to do that work for you:
            CREATE OR REPLACE PROCEDURE replace_binds (
               p_sql_in    IN       VARCHAR2,
               p_sql_out   OUT      VARCHAR2
            )
            IS
               v_sql      VARCHAR2 (32767);
               v_names    DBMS_SQL.varchar2_table;
               v_pos      NUMBER;
               v_length   NUMBER;
               v_exit     NUMBER;
            BEGIN
               v_sql := p_sql_in;
               v_names := wwv_flow_utilities.get_binds (v_sql);
            
               FOR i IN 1 .. v_names.COUNT
               LOOP
            
                  <<do_it_again>>
                  v_pos := INSTR (LOWER (v_sql), LOWER (v_names (i)));
                  v_length := LENGTH (LOWER (v_names (i)));
                  v_sql :=
                        SUBSTR (v_sql, 1, v_pos - 1)
                     || v_names (i)
                     || SUBSTR (v_sql, v_pos + v_length);
                  v_sql :=
                     REPLACE (v_sql,
                              UPPER (v_names (i)),
                              'v(''' || LTRIM (v_names (i), ':') || ''')'
                             );
            
                  IF INSTR (LOWER (v_sql), LOWER (v_names (i))) > 0
                  THEN
                     GOTO do_it_again;
                  END IF;
               END LOOP;
            
               p_sql_out := v_sql;
            END replace_binds;
            Denes Kubicek
            -------------------------------------------------------------------
            http://deneskubicek.blogspot.com/
            http://htmldb.oracle.com/pls/otn/f?p=31517:1
            -------------------------------------------------------------------
            • 78. Re: APEX 3.1 Enhancements
              Arie Geller
              Hello,

              Two more enhancement requests, regarding the SQL Workshop:

              SQL Commands – The current save and run buttons are located on the right hand side of the screen. The problem is that when you are working with a table, which include large number of columns, you need to scroll all the way to the right in order to run your query. This can be very annoying after the second time.

              I believe it would be more productive to locate these buttons right after the clear and find icons on the left hand side of the screen. If the uniformity of this part of the screen must be maintained, I believe these buttons can be transferred into icons (in the style of SQL Developer for example). If you don't want to move/delete these buttons from their current position, maybe it would be possible to add the icons, in addition to the buttons.

              Object Browser – If we are dealing with multiple columns tables, the current Object Browser display, in the data tab, only the first 31 columns. If this is not some "must" limitation (for reasons I'm not aware of) it would be nice to see all the table columns on this view.

              Thanks,
              Arie.
              • 79. Re: APEX 3.1 Enhancements
                Phil UK
                Denes - thanks for this but I'd simply concatenate based on the v function syntax if I wanted this. I was after a way of addressing performance so that the same SQL was kept in the shared pool as is catered for using SQL with binds normally which is not possible with collection queries.

                Phil
                • 80. Re: APEX 3.1 Enhancements
                  Denes Kubicek
                  Phil,

                  I do not understand this:

                  "...thanks for this but I'd simply concatenate based on the v function syntax if I wanted this".

                  The query performance issues are valid.

                  Denes Kubicek
                  -------------------------------------------------------------------
                  http://deneskubicek.blogspot.com/
                  http://htmldb.oracle.com/pls/otn/f?p=31517:1
                  -------------------------------------------------------------------
                  • 81. Re: APEX 3.1 Enhancements
                    Phil UK
                    Hi Denes - if I wanted just SQL to construct a collection from a query then I'd just do a "select x,y,z from table_name where id='||v(P123_ID" type query.

                    However, in a system where this might be ocurring a lot, I'd like to use a true bind using the "using" syntax so that the SQL generated could be resued and performance improved.

                    Phil
                    • 82. Re: APEX 3.1 Enhancements
                      Denes Kubicek
                      O.K. I understand. You mean manually change the query. Could be a pain if the query is
                      big.

                      To your request. I am trying to understand what your are asking for. However, I can not see
                      the way to accomplish that. How would you solve that problem?

                      Denes Kubicek
                      -------------------------------------------------------------------
                      http://deneskubicek.blogspot.com/
                      http://htmldb.oracle.com/pls/otn/f?p=31517:1
                      -------------------------------------------------------------------
                      • 83. Re: APEX 3.1 Enhancements
                        Phil UK
                        Hi Denes - I have a work around which is to construct the SQL by concatenation as in the old days with VB but I mentioned this a while back and someone from Oracle acknowledged it would be an enhancement to allow the same SQL to be used via bind variables.
                        It is no show stopper but just another way of improving performance and lessening load on the DB to parse SQL each time.
                        We'll see what happens with 3.1/3.2 eh!?
                        • 84. Re: APEX 3.1 Enhancements
                          135285
                          It would be useful that buttons which are "displayed among region's items" have some additional alignment options as normal page items have (btw, they are stored as page items anyway).

                          Currently it's necessary to write some strange Javascript code to be able to change the TD cell. See Re: Fields Side By Side

                          I'm looking for
                          -) Horizontal / Vertical Alignment
                          -) HTML Table Cell Attributes

                          BTW, why is the "Pre Element Text" property missing for buttons, looks like that this one got missed when this new property was added in APEX 3.0

                          Patrick
                          ----------------------------------------------------------------------------------------------------
                          My APEX Blog: http://inside-apex.blogspot.com
                          The ApexLib Framework: http://apexlib.sourceforge.net
                          The APEX Builder Plugin: http://sourceforge.net/projects/apexplugin/
                          • 85. Re: APEX 3.1 Enhancements
                            Phil UK
                            When I create a LOV (which is essentially a SQL query) I sometimes create a default. However, for a default I have to use a PL/SQL expression. I can do this but why not just make a default option available which is a SQL expression rather than a function body?
                            • 86. Re: APEX 3.1 Enhancements
                              437788
                              I might suggest that a HTML Editor, like the fckeditor could be optional to use in HTML Regions and other Regions that feature a HTML Header and Footer.

                              These are places where I might put instructions on how to use the region for example, and having an easy means to place formatted text would be very helpful and time saving.

                              Needless to say, it should work with all common web browsers, not just IE.
                              • 87. Re: APEX 3.1 Enhancements
                                437788
                                On the theme of HTML Editors, is it feasible to include a Grammar Checker in addtional to the Spell Checker of the respective HTML Editor?
                                • 88. Re: APEX 3.1 Enhancements
                                  575309
                                  We would like to see some of the quirks that we are experiencing due to a reverse proxy front end configuration resolved =)

                                  Great work by the way!
                                  Shawn
                                  http://www.appshosting.com
                                  • 89. Re: APEX 3.1 Enhancements
                                    135285
                                    The new APEX Dictionary View Browser (Utilities\APEX Dictionary) should have a "Execute" button in the "Query Columns" and "Query Conditions" section.

                                    Now you have to scroll to the top of the page to press the "Go" button, in case the column or the query condition has changed.

                                    Thanks
                                    Patrick
                                    ----------------------------------------------------------------------------------------------------
                                    My APEX Blog: http://inside-apex.blogspot.com
                                    The ApexLib Framework: http://apexlib.sourceforge.net
                                    The APEX Builder Plugin: http://sourceforge.net/projects/apexplugin/
                                    1 4 5 6 7 8 Previous Next