Problems with partial trigger

I have a button "Edit" in the box for which submit partial is enabled. When I click that button, I want to make the button 'Save' outside of the box and when click on the "Save" button I want to make the change and hide him save button button. I put partial triggers at the level of the Panel for these two buttons box. Then click on the button Edit, I'm able to hide the edit button, but unable to make the record button. I suspect this partial trigger on Panel box does not apply to components outside of the Panel. Please advise something to achieve.

Thank you
Satya

Satya, please indicate your jdev version!

Have you used the rendered property or the visible property to show or hide the buttons?
You use the visible property for this to work. Your backup need button a partial trigger tuned on the button modify and edit button one listen to the record button.

Timo

Tags: Java

Similar Questions

  • What is the problem with my trigger :(

    Hi friends

    What is the problem with this trigger please
    SQL> select object_type from user_objects where object_name='CE_STMT_INT_TMP';
    
    OBJECT_TYPE
    -------------------
    TABLE
    
    SQL> create or replace trigger ce_stmt_int_tmp_trg1
      2  after insert on ce_stmt_int_tmp
      3  for each row
      4  begin
      5      :new.column7 := 'checkno_test';
      6  end;
      7  /
    create or replace trigger ce_stmt_int_tmp_trg1
                              *
    ERROR at line 1:
    ORA-04084: cannot change NEW values for this trigger type
    Thank you very much

    I guess you mean that SQL * Loader is insertion of the value of the column, not not to date. You can override the value SQL * Loader is the insertion in a level line BEFORE INSERT trigger.

    Justin

  • Problem with partial dataset HDF5 readings

    I'm having a problem finding how by a partial read of a dataset using LVHDF5 Jason S HDF5. I can save a dataset to a file and I can read it on a whole, but I can't understand how to read a part of it. For example

    :

    I save a 235 x 235 x 1024 dataset in a file. I want to read a 5 x 5 x 1024 picture of this dataset. I'll try the following:

    -use H5Dopen.vi to open the dataset

    -use H5Dget_space.vi to get a reference to a data space I guess (guess) is associated with the dataset object data space

    -Use H5Sselect_hyperslab.vi to choose my 5 x 5 x 1024 part by using the 'block '. My place of departure is 0,0,0 and stride count are 1,1,1
    -Create a DataSpace.vi of correspondence to create a data space which is 5 x 5 x 1024 in size, with the same data type that my dataset (float).

    -read the data in the "hyperslab" in a table using H5Dread.vi, followed by the function Variant Data.

    If I don't file, H5Dread.vi space entry wiring reads the entire data set.  However, if I try to use the obtained reference w / H5Dget_space.vi, as the space of file, I get an error of alternative to data that says "the variant data type is not compatible with the data type of wired for the input type.".

    I'd appreciate any help in getting this work.

    AHA. I found my problem. I use H5Dselect_hyperslab in my memory and the space of my file.

  • Problem with partially the image to an image that is on the page

    Hi all

    I have a graphic image that partially overlaps the page, as follows:

    15-02-2016 13-12-50.png

    When I am trying to place an image by script, I get an error: 'this value would cause one or more objects to leave the editing table. However, I can place manually in InDesign with no problems. I wonder why I am unable to do this by the script.

    Main();
    
    function Main() {
        var doc = app.activeDocument;
        var imgFile = new File("~/Desktop/Test.jpg");
        // Select the rectangle to place the image
        var rec = app.selection[0];
        try {
            var img = rec.place(imgFile);
        }
        catch(err) {
            $.writeln(err.message + ", line: " + err.line);
        }
    }
    

    From the top of my head, a workaround solution - in the catch block, follow these steps:

    1. Remember original geometric boundaries of the framework
    2. adjust the problem setting in the centre of the page
    3. Place the image
    4. Move the rear frame to its original position

    Maybe someone can suggest a more elegant solution?

    Here's the indd file , I used for the test.

    Kind regards

    Kasyan

    The sample file is CC 2014, but also confirmed for CS4. So, at least, this is a long-standing bug.

    Moreover, the rotation has nothing to do with it. Any part of a target frame that comes out of the page and the Whiteboard in gray nothingness between spreads will lead to this error.

    Fact the editing table option?

  • Having a problem with the trigger. (need help)

    Hi all

    I m totally new to the PL/SQL... hope someone can help me with this...

    I am now using the trigger to block insertion in the 'attendance99' table when records reach the maximum limit and insert the record in the table «waiting_list»
    The problem I encounter is using RAISE_APPLICATION_ERROR, it will block the insertion at the table "waiting_list" as well...
    I try to only use the DBMS_OUTPUT. Put_line instead, but end by > > > inserting record in the table 'presences' so many tables "waiting_list.



    -------------------------------------------------------------
    CREATE OR REPLACE TRIGGER trig_attendance
    Before Insert on attendance99
    Referring again like new
    for each line
    DECLARE
    maxstud NUMBER (2);
    currstud NUMBER (2);
    Begin
    SELECT COUNT (*) INTO currstud FROM attendance99 WHERE offering_id =:New.offering_id;
    SELECT max_no_students INTO maxstud to offer WHERE the offering_id =:New.offering_id;
    IF currstud > = maxstud
    THEN
    insert_waitinglist (: new .offering_id,: New.student_id,: New.evaluation,: New.amount_paid);
    RAISE_APPLICATION_ERROR (-20500, ' sorry, this offering ID has reach maximum students, you will be placed in queue! ");
    END IF;
    END;
    /
    ---------------------------------------------

    CREATE OR REPLACE PROCEDURE insert_waitinglist
    (v_offeringid IN waiting_list.offering_id%TYPE,
    v_studentid IN waiting_list.student_id%TYPE,
    v_evaluation IN waiting_list.evaluation%TYPE,
    v_amountpaid IN waiting_list.amount_paid%TYPE)
    IS
    BEGIN

    INSERT INTO waiting_list (student_id, assessment, offering_id, amount_paid)
    VALUES (v_offeringid, v_studentid, v_evaluation, v_amountpaid);
    END insert_waitinglist;
    /
    -----------------------------------------------

    Hello

    Try this:

    CREATE OR REPLACE PROCEDURE insert_waitinglist(v_offeringid IN waiting_list.offering_id%TYPE,
                                                   v_studentid  IN waiting_list.student_id%TYPE,
                                                   v_evaluation IN waiting_list.evaluation%TYPE,
                                                   v_amountpaid IN waiting_list.amount_paid%TYPE) IS
        PRAGMA AUTONOMOUS_TRANSACTION;
    BEGIN
    
        INSERT INTO waiting_list
            (offering_id,
             student_id,
             evaluation,
             amount_paid)
        VALUES
            (v_offeringid,
             v_studentid,
             v_evaluation,
             v_amountpaid);
    
        COMMIT;
    END insert_waitinglist;
    /
    

    Kind regards

    Published by: Walter Fernández on April 15, 2009 10:10 - missing ';', sorry

  • Problem with TTL trigger

    Hello everyone,

    I try to start acquiring the image of a TTL pulse generated in Labview (PIV). I have a TTL signal (I hope it's TTL) generated through devices to the switch to zero of a periodic signal, type sinewave 1.42 Hz [I use PXI 6221 Council with SC-2345 (with FT01 connected to the BNC port), TTL comes of the FT01].

    After connecting to the input TTL trigger, the amplitude of the voltage is 5V to 4.77V falls. The trigger seems to work occasionally, but not always. I contacted the company that we provided the image acquisition hardware/software and they mentioned that TTL [(0-5 V onde carrée)] must be at least 5 Hz. This confuses me a little because I don't really know how to control the TTL frequency and if my code can accommodate for this and I'm starting to doubt my code as well.

    I have attached my code for reference, if anyone can give me a hand I would really appreciate it.

    Thanks in advance!

    Alex

    Oleks,

    There are a few things that need to be changed. First of all, your task of counter, you enter in the while loop and check if something is true or false. If it's wrong you stop the task, but in the case of true you never repeat the task. You will need to start the job in the State to resume. In addition, you will want to place a control task.vi DAQmx after schedule vi and set it to commit. This will ensure that your task running as soon as possible after the judgment of the task it with no re - check all data before running again.

    -Travis E

  • problem with partial update on linux

    Hello

    When a partial update is executed every time, the siz of the process dgaph in memory increases about 200 MB. Initially when just ran the update of the base, the siz of the dgraph was about 1 GB, but after a few partial updates the memory went up to 2.5 GB dgraph. However we have not inserted/updated during the partial run, each updates were in 50 records. If the dgraph is restarted, then the siz of the process boils down to 1 GB. Also after the partial update, query response time is also get degraded.

    Please let me know someone has encountered this problem and also the solution that you can recommend.

    Thank you
    RP

    The script of global warming is essentially a script replay queries frequently used to your dgraph to warm the cache. One way to get commonly used queries is to analyze your logs of application of production dgraph. You would like to experiment the number of queries that you use in your global warming script to install in your partial window of 20 minutes.

  • Performance problems with partial extraction of XML-structure

    Hello

    I want to extract partial XML Structures of an XML document, but I met some performance issues with some (larger) documents.
    Select it slow is the following:
    SELECT EXTRACT( xmldoc, '/adwsroot/lagerblock/lager/lagerzeile[pzn=''' || :a || ''']').getClobVal()
    FROM t_apoxml
    CREATE TABLE T_APOXML
     (ID         NUMBER(10,0)  NOT NULL
     ,STATUS     NUMBER(1)     DEFAULT 0
     ,XMLDOC_BEZ VARCHAR2(100) DEFAULT 'n.a.' NOT NULL
     ,XMLDOC     SYS.XMLTYPE   NOT NULL
     ,DATE_INS   DATE          NOT NULL
     ,DATE_UPD   DATE          NOT NULL
     ,DATE_EXT   DATE          NOT NULL
          ) XMLTYPE COLUMN XMLDOC store AS OBJECT RELATIONAL 
                                  XMLSCHEMA "AdasDws3.xsd"  
                                  ELEMENT "adwsroot"
    The XSD is as follows:
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns="http://www.adas.de/spec/dws/v1" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.adas.de/spec/dws/v1" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0">
         <xs:annotation>
              <xs:documentation>ADAS-DataWarehouse-Schnittstelle Datenlieferung Ausbaustufe 3 - Version 1.0</xs:documentation>
         </xs:annotation>
         <xs:include schemaLocation="AdasDwsTypes.xsd"/>
         <xs:element name="adwsroot">
              <xs:annotation>
                   <xs:documentation>Root-Element</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="kopf" type="Kopf"/>
                        <xs:element name="verkaufsblock">
                             <xs:annotation>
                                  <xs:documentation>Element für die Verkaufsdaten in Ausbaustufe 3</xs:documentation>
                             </xs:annotation>
                             <xs:complexType>
                                  <xs:choice maxOccurs="unbounded">
                                       <xs:element name="total" type="Total"/>
                                       <xs:element name="keineDaten" type="xs:dateTime"/>
                                  </xs:choice>
                             </xs:complexType>
                        </xs:element>
                        <xs:element name="wareneingangsblock">
                             <xs:annotation>
                                  <xs:documentation>Element für die Wareneingangsdaten in Ausbaustufe 3</xs:documentation>
                             </xs:annotation>
                             <xs:complexType>
                                  <xs:choice maxOccurs="unbounded">
                                       <xs:element name="wareneingang" type="Wareneingang"/>
                                       <xs:element name="keineDaten" type="xs:dateTime"/>
                                  </xs:choice>
                             </xs:complexType>
                        </xs:element>
                        <xs:element name="retourenblock">
                             <xs:annotation>
                                  <xs:documentation>Element für die Retourendaten in Ausbaustufe 3</xs:documentation>
                             </xs:annotation>
                             <xs:complexType>
                                  <xs:choice maxOccurs="unbounded">
                                       <xs:element name="retoure" type="Retoure"/>
                                       <xs:element name="keineDaten" type="xs:dateTime"/>
                                  </xs:choice>
                             </xs:complexType>
                        </xs:element>
                        <xs:element name="neinverkaufsblock">
                             <xs:annotation>
                                  <xs:documentation>Element für die Neinverkaufsdaten in Ausbaustufe 3</xs:documentation>
                             </xs:annotation>
                             <xs:complexType>
                                  <xs:choice maxOccurs="unbounded">
                                       <xs:element name="neinverkauf" type="Neinverkauf"/>
                                       <xs:element name="keineDaten" type="xs:dateTime"/>
                                  </xs:choice>
                             </xs:complexType>
                        </xs:element>
                        <xs:element name="lagerblock">
                             <xs:annotation>
                                  <xs:documentation>Element für die Lagerdaten in Ausbaustufe 3</xs:documentation>
                             </xs:annotation>
                             <xs:complexType>
                                  <xs:choice maxOccurs="unbounded">
                                       <xs:element name="lager" type="Lager"/>
                                       <xs:element name="keineDaten" type="xs:dateTime"/>
                                  </xs:choice>
                             </xs:complexType>
                        </xs:element>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:complexType name="Total">
              <xs:annotation>
                   <xs:documentation>Typ für das Total in Ausbaustufe 3</xs:documentation>
              </xs:annotation>
              <xs:complexContent>
                   <xs:extension base="TotalBasis">
                        <xs:sequence>
                             <xs:element name="subtotal" type="Subtotal" maxOccurs="unbounded"/>
                        </xs:sequence>
                   </xs:extension>
              </xs:complexContent>
         </xs:complexType>
         <xs:complexType name="Subtotal">
              <xs:annotation>
                   <xs:documentation>Typ für das Subtotal in Ausbaustufe 3</xs:documentation>
              </xs:annotation>
              <xs:complexContent>
                   <xs:extension base="SubtotalBasisMitPerson">
                        <xs:sequence>
                             <xs:element name="subtotalzeile" type="Subtotalzeile" maxOccurs="unbounded"/>
                        </xs:sequence>
                   </xs:extension>
              </xs:complexContent>
         </xs:complexType>
         <xs:complexType name="Subtotalzeile">
              <xs:annotation>
                   <xs:documentation>Typ für die Subtotalzeile in Ausbaustufe 3</xs:documentation>
              </xs:annotation>
              <xs:complexContent>
                   <xs:extension base="SubtotalzeileBasis">
                        <xs:sequence>
                             <xs:group ref="Eigenpreisinfo"/>
                        </xs:sequence>
                   </xs:extension>
              </xs:complexContent>
         </xs:complexType>
         <xs:complexType name="Neinverkauf">
              <xs:annotation>
                   <xs:documentation>Typ für den Neinverkauf (Nachfrage ohne Bestellung) in Ausbaustufe 3</xs:documentation>
              </xs:annotation>
              <xs:complexContent>
                   <xs:extension base="NeinverkaufBasis">
                        <xs:sequence>
                             <xs:element name="neinverkaufszeile" type="Neinverkaufszeile" maxOccurs="unbounded"/>
                        </xs:sequence>
                   </xs:extension>
              </xs:complexContent>
         </xs:complexType>
         <xs:complexType name="Neinverkaufszeile">
              <xs:annotation>
                   <xs:documentation>Typ für die Neinverkaufszeile (Nachfrage ohne Bestellung) in Ausbaustufe 3</xs:documentation>
              </xs:annotation>
              <xs:complexContent>
                   <xs:extension base="NeinverkaufszeileBasis">
                        <xs:sequence>
                             <xs:group ref="Eigenpreisinfo"/>
                        </xs:sequence>
                   </xs:extension>
              </xs:complexContent>
         </xs:complexType>
         <xs:complexType name="Wareneingang">
              <xs:annotation>
                   <xs:documentation>Typ für den Wareneingang in Ausbaustufe 3</xs:documentation>
              </xs:annotation>
              <xs:complexContent>
                   <xs:extension base="WareneingangBasis">
                        <xs:sequence>
                             <xs:element name="wareneingangszeile" type="Wareneingangszeile" maxOccurs="unbounded"/>
                        </xs:sequence>
                   </xs:extension>
              </xs:complexContent>
         </xs:complexType>
         <xs:complexType name="Wareneingangszeile">
              <xs:annotation>
                   <xs:documentation>Typ für die Wareneingangszeile in Ausbaustufe 3</xs:documentation>
              </xs:annotation>
              <xs:complexContent>
                   <xs:extension base="WareneingangszeileBasis">
                        <xs:sequence>
                             <xs:group ref="Eigenpreisinfo"/>
                        </xs:sequence>
                   </xs:extension>
              </xs:complexContent>
         </xs:complexType>
         <xs:complexType name="Retoure">
              <xs:annotation>
                   <xs:documentation>Typ für die Retoure in Ausbaustufe 3</xs:documentation>
              </xs:annotation>
              <xs:complexContent>
                   <xs:extension base="RetoureBasis">
                        <xs:sequence>
                             <xs:element name="retourenzeile" type="Retourenzeile" maxOccurs="unbounded"/>
                        </xs:sequence>
                   </xs:extension>
              </xs:complexContent>
         </xs:complexType>
         <xs:complexType name="Retourenzeile">
              <xs:annotation>
                   <xs:documentation>Typ für die Retourenzeile in Ausbaustufe 3</xs:documentation>
              </xs:annotation>
              <xs:complexContent>
                   <xs:extension base="RetourenzeileBasis">
                        <xs:sequence>
                             <xs:group ref="Eigenpreisinfo"/>
                        </xs:sequence>
                   </xs:extension>
              </xs:complexContent>
         </xs:complexType>
         <xs:complexType name="Lager">
              <xs:annotation>
                   <xs:documentation>Typ für das Lager in Ausbaustufe 3</xs:documentation>
              </xs:annotation>
              <xs:complexContent>
                   <xs:extension base="LagerBasis">
                        <xs:sequence>
                             <xs:element name="lagerzeile" type="Lagerzeile" maxOccurs="unbounded"/>
                        </xs:sequence>
                   </xs:extension>
              </xs:complexContent>
         </xs:complexType>
         <xs:complexType name="Lagerzeile">
              <xs:annotation>
                   <xs:documentation>Typ für die Lagerzeile in Ausbaustufe 3</xs:documentation>
              </xs:annotation>
              <xs:complexContent>
                   <xs:extension base="LagerzeileBasis">
                        <xs:sequence>
                             <xs:group ref="Eigenpreisinfo"/>
                        </xs:sequence>
                   </xs:extension>
              </xs:complexContent>
         </xs:complexType>
    </xs:schema>
    and depends on another schema (its kind of long but if you need I'll post).

    Before recording, I annotate the schema with:
    DBMS_XMLSCHEMA_ANNOTATE.setTimeStampWithTimeZone( xXsdData );
    DBMS_XMLSCHEMA_ANNOTATE.SETDEFAULTTABLE ( xXsdData, 'adwsroot', 'XML_ADWSROOT', TRUE );
    Example of a document with select fast; the document contains a ~ 21000 < lagerzeile > - blocks:
    <?xml version="1.0" encoding="iso-8859-1"?>
    <adwsroot xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.adas.de/spec/dws/v1">
      <kopf>
        <version>1.0</version>
        <absender>1234567</absender>
        <erstelltAm>2012-02-18T01:08:03.342</erstelltAm>
        <instanzId>0</instanzId>
        <system>
          <anbieter>VSA ApothekenSysteme GmbH</anbieter>
          <systembezeichnung>Pharmasoft, Infopharm, Wabe, jump</systembezeichnung>
        </system>
      </kopf>
      <verkaufsblock>
        <keineDaten>2012-02-13T00:00:00</keineDaten>
      </verkaufsblock>
      <wareneingangsblock>
        <keineDaten>2012-02-14T00:00:00</keineDaten>
      </wareneingangsblock>
      <retourenblock>
        <keineDaten>2012-02-15T00:00:00</keineDaten>
      </retourenblock>
      <neinverkaufsblock>
        <keineDaten>2012-02-16T00:00:00</keineDaten>
      </neinverkaufsblock>
      <lagerblock>
        <lager>
          <StandVom>2012-02-16T00:00:00.0</StandVom>
          <lagerzeile>
              <pzn>1001094</pzn>
              <name><![CDATA[HOT THERMO dura C Creme]]></name>
              <menge>50</menge>
              <einheit>g</einheit>
              <ampreisvAmg>1</ampreisvAmg>
              <ampreisvSgb>2</ampreisvSgb>
              <btm>1</btm>
              <abdaWarengruppe>AM02AB01</abdaWarengruppe>
              <darreichungsform>CRE</darreichungsform>
              <anbieter>19422</anbieter>
              <lagertemperaturMin>0</lagertemperaturMin>
              <lagertemperaturMax>0</lagertemperaturMax>
              <notfalldepot>0</notfalldepot>
              <abgaberegelung>Apothekenpflicht</abgaberegelung>
              <artikelart>Arzneimittel</artikelart>
              <mwstsatz>19.00</mwstsatz>
              <listenEk>223</listenEk>
              <listenVk>430</listenVk>
              <notfalldepotEigen>false</notfalldepotEigen>
              <anLager>true</anLager>
              <kalkulierterVk>0</kalkulierterVk>
              <platzierung>keine</platzierung>
              <lagerort>Kein Lagerartikel</lagerort>
            <bestand>0</bestand>
            <fruehesterVerfall>9999-12-31T00:00:00.0</fruehesterVerfall>
            <bewirtschaftungssart>Besorger</bewirtschaftungssart>
            <nnek>0</nnek>
          </lagerzeile>
        </lager>
        <lager>
          <StandVom>2012-02-16T00:00:00.0</StandVom>
          <lagerzeile>
              <pzn>2487443</pzn>
              <name><![CDATA[BALKIS Nasentropfen f.Kinder 0,05%]]></name>
              <menge>10</menge>
              <einheit>ml</einheit>
              <ampreisvAmg>1</ampreisvAmg>
              <ampreisvSgb>2</ampreisvSgb>
              <btm>1</btm>
              <abdaWarengruppe>AR01AA07</abdaWarengruppe>
              <darreichungsform>NTR</darreichungsform>
              <anbieter>06170</anbieter>
              <lagertemperaturMin>0</lagertemperaturMin>
              <lagertemperaturMax>0</lagertemperaturMax>
              <notfalldepot>0</notfalldepot>
              <abgaberegelung>Apothekenpflicht</abgaberegelung>
              <artikelart>Arzneimittel</artikelart>
              <mwstsatz>19.00</mwstsatz>
              <listenEk>130</listenEk>
              <listenVk>253</listenVk>
              <notfalldepotEigen>false</notfalldepotEigen>
              <anLager>true</anLager>
              <kalkulierterVk>0</kalkulierterVk>
              <platzierung>keine</platzierung>
              <lagerort>Kein Lagerartikel</lagerort>
            <bestand>0</bestand>
            <fruehesterVerfall>9999-12-31T00:00:00.0</fruehesterVerfall>
            <bewirtschaftungssart>Besorger</bewirtschaftungssart>
            <nnek>0</nnek>
          </lagerzeile>
        </lager>
        <lager>
          <StandVom>2012-02-16T00:00:00.0</StandVom>
          <lagerzeile>
              <pzn>1218066</pzn>
              <name><![CDATA[KEPPRA 500 mg Filmtabletten]]></name>
              <menge>200</menge>
              <einheit>St</einheit>
              <ampreisvAmg>2</ampreisvAmg>
              <ampreisvSgb>1</ampreisvSgb>
              <btm>1</btm>
              <abdaWarengruppe>AN03AX14</abdaWarengruppe>
              <darreichungsform>FTA</darreichungsform>
              <anbieter>32015</anbieter>
              <lagertemperaturMin>0</lagertemperaturMin>
              <lagertemperaturMax>0</lagertemperaturMax>
              <notfalldepot>0</notfalldepot>
              <abgaberegelung>Verschreibungspflicht</abgaberegelung>
              <artikelart>Arzneimittel</artikelart>
              <mwstsatz>19.00</mwstsatz>
              <listenEk>29839</listenEk>
              <listenVk>37537</listenVk>
              <notfalldepotEigen>false</notfalldepotEigen>
              <anLager>true</anLager>
              <kalkulierterVk>0</kalkulierterVk>
              <platzierung>keine</platzierung>
              <lagerort>Kein Lagerartikel</lagerort>
            <bestand>0</bestand>
            <fruehesterVerfall>9999-12-31T00:00:00.0</fruehesterVerfall>
            <bewirtschaftungssart>Besorger</bewirtschaftungssart>
            <nnek>0</nnek>
          </lagerzeile>
        </lager>
      </lagerblock>
    </adwsroot>
    I've already renamed the nested tables (renamecollectiontable) and saw the BEACHES of analyses in terms of the explain command. I created a few index on the referenced tables, but the plan has not changed at all. I think I'm still too inexperienced with XMLDB.
    Anyone has any advice for me?
    I can give you additional information?
    Object / relational is perhaps not the best choice?


    --------------------------------------------------------------------------------
    Oracle Database 11 g Enterprise Edition Release 11.2.0.1.0 - 64 bit Production
    PL/SQL Release 11.2.0.1.0 - Production
    CORE 11.2.0.1.0 Production
    AMT for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production
    NLSRTL Version 11.2.0.1.0 - Production

    Alex,

    I don't have your version, but here are my tests on 11.2.0.3:

    Schema records with:

    begin
     dbms_xmlschema.registerSchema(
       schemaURL => 'AdasDwsTypes.xsd'
     , schemaDoc => bfilename('TEST_DIR', 'AdasDwsTypes.xsd')
     , local => true
     , genTypes => true
     , genTables => false
     , enableHierarchy => dbms_xmlschema.ENABLE_HIERARCHY_NONE
     , csid => nls_charset_id('AL32UTF8')
     );
    end;
    /
    
    declare
     v_schema xmltype := xmltype(bfilename('TEST_DIR', 'AdasDws.xsd'),nls_charset_id('WE8ISO8859P1'));
    begin
     dbms_xmlschema_annotate.setTimeStampWithTimeZone(v_schema);
    
     dbms_xmlschema.registerSchema(
       schemaURL => 'AdasDws.xsd'
     , schemaDoc => v_schema
     , local => true
     , genTypes => true
     , genTables => false
     , enableHierarchy => dbms_xmlschema.ENABLE_HIERARCHY_NONE
     );
    end;
    /
    

    Creating table...

    CREATE TABLE T_APOXML (
      ID         NUMBER(10)    NOT NULL
    , XMLDOC     XMLTYPE       NOT NULL
    )
    XMLTYPE COLUMN XMLDOC store AS OBJECT RELATIONAL
    XMLSCHEMA "AdasDws.xsd"
    ELEMENT "adwsroot"
    ;
    

    ... and rename the nested tables of interest:

    begin
     dbms_xmlstorage_manage.renameCollectionTable(
       tab_name => 'T_APOXML'
     , col_name => 'XMLDOC'
     , xpath => '"XMLDATA"."lagerblock"."lager"'
     , collection_table_name => 'T_APOXML_LAGER'
     );
    end;
    /
    
    begin
     dbms_xmlstorage_manage.renameCollectionTable(
       tab_name => 'T_APOXML_LAGER'
     , xpath => 'lagerzeile'
     , collection_table_name => 'T_APOXML_LAGERZEILE'
     );
    end;
    /
    

    Index on "pzn":

    create index T_APOXML_LAGERZEILE_idx on T_APOXML_LAGERZEILE ("pzn");
    

    Queries (remember the stats):

    SQL> set timing on
    SQL> insert into t_apoxml (id, xmldoc)
      2  values(1, xmltype(bfilename('TEST_DIR', 'ADAS_sample.xml'),nls_charset_id('WE8ISO8859P1')))
      3  ;
    
    1 row created.
    
    Elapsed: 00:00:10.03
    SQL> commit;
    
    Commit complete.
    
    Elapsed: 00:00:00.00
    SQL> exec dbms_stats.gather_table_stats(user, 'T_APOXML');
    
    PL/SQL procedure successfully completed.
    
    Elapsed: 00:00:02.54
    SQL> set autotrace traceonly explain
    SQL> set lines 120
    SQL> SELECT xmlquery(
      2          'declare default element namespace "http://www.adas.de/spec/dws/v1"; (::)
      3          /adwsroot/lagerblock/lager/lagerzeile[pzn=$pzn]'
      4          passing xmldoc
      5                , cast( 1001094 as number ) as "pzn"
      6          returning content
      7         )
      8  FROM t_apoxml
      9  WHERE id = 1
     10  ;
    Elapsed: 00:00:00.00
    
    Execution Plan
    ----------------------------------------------------------
    Plan hash value: 1388369865
    
    -------------------------------------------------------------------------------------------------------------
    | Id  | Operation                     | Name                        | Rows  | Bytes | Cost (%CPU)| Time     |
    -------------------------------------------------------------------------------------------------------------
    |   0 | SELECT STATEMENT              |                             |     1 |   173 |     3   (0)| 00:00:01 |
    |   1 |  SORT GROUP BY                |                             |     1 |  4603 |            |       |
    |   2 |   NESTED LOOPS                |                             |     1 |  4603 |     3   (0)| 00:00:01 |
    |   3 |    TABLE ACCESS BY INDEX ROWID| T_APOXML_LAGERZEILE         |     1 |  4570 |     2   (0)| 00:00:01 |
    |*  4 |     INDEX RANGE SCAN          | T_APOXML_LAGERZEILE_IDX     |     1 |       |     1   (0)| 00:00:01 |
    |*  5 |    TABLE ACCESS BY INDEX ROWID| T_APOXML_LAGER              |     1 |    33 |     1   (0)| 00:00:01 |
    |*  6 |     INDEX UNIQUE SCAN         | T_APOXML_LAGERZEILE_MEMBERS |     1 |       |     0   (0)| 00:00:01 |
    |*  7 |  TABLE ACCESS FULL            | T_APOXML                    |     1 |   173 |     3   (0)| 00:00:01 |
    -------------------------------------------------------------------------------------------------------------
    
    Predicate Information (identified by operation id):
    ---------------------------------------------------
    
       4 - access("pzn"=1001094)
       5 - filter("NESTED_TABLE_ID"=:B1)
       6 - access("NESTED_TABLE_ID"="SYS_ALIAS_4"."SYS_NC0000700008$")
       7 - filter("ID"=1)
    
    Note
    -----
       - dynamic sampling used for this statement (level=2)
    
    SQL> SELECT xmlquery(
      2          'declare default element namespace "http://www.adas.de/spec/dws/v1"; (::)
      3          /adwsroot/lagerblock/lager/lagerzeile[pzn=$pzn]'
      4          passing xmldoc
      5                , cast( 2487443 as number ) as "pzn"
      6          returning content
      7         )
      8  FROM t_apoxml
      9  WHERE id = 1
     10  ;
    Elapsed: 00:00:00.00
    
    Execution Plan
    ----------------------------------------------------------
    Plan hash value: 1086728381
    
    -----------------------------------------------------------------------------------------------------
    | Id  | Operation                     | Name                | Rows  | Bytes | Cost (%CPU)| Time     |
    -----------------------------------------------------------------------------------------------------
    |   0 | SELECT STATEMENT              |                     |     1 |   173 |     3   (0)| 00:00:01 |
    |   1 |  SORT GROUP BY                |                     |     1 |  4603 |            |          |
    |*  2 |   HASH JOIN                   |                     |   172 |   773K|   177   (1)| 00:00:03 |
    |   3 |    TABLE ACCESS BY INDEX ROWID| T_APOXML_LAGER      |   172 |  5676 |     6   (0)| 00:00:01 |
    |*  4 |     INDEX RANGE SCAN          | SYS_C0011899        |    69 |       |     2   (0)| 00:00:01 |
    |*  5 |    TABLE ACCESS FULL          | T_APOXML_LAGERZEILE | 18058 |    78M|   171   (1)| 00:00:03 |
    |*  6 |  TABLE ACCESS FULL            | T_APOXML            |     1 |   173 |     3   (0)| 00:00:01 |
    -----------------------------------------------------------------------------------------------------
    
    Predicate Information (identified by operation id):
    ---------------------------------------------------
    
       2 - access("NESTED_TABLE_ID"="SYS_ALIAS_4"."SYS_NC0000700008$")
       4 - access("NESTED_TABLE_ID"=:B1)
       5 - filter("pzn"=2487443)
       6 - filter("ID"=1)
    
    Note
    -----
       - dynamic sampling used for this statement (level=2)
    

    For the first query, the index is used and the execution time is very short.
    For the second query from pzn = 2487443, the optimizer chooses a full analysis, because all pzns, but two are equal to 2487443. The execution time is a little longer (4 seconds on my system) because of the amount of lines to back aggregated in a fragment of XMLType.

    A couple more:

    SQL> set autotrace on explain
    SQL> SELECT l1_lager.pzn AS PZN
      2       , count(*)
      3  FROM t_apoxml t
      4     , XMLTABLE(
      5         XMLNamespaces(default 'http://www.adas.de/spec/dws/v1')
      6       , '/adwsroot/lagerblock/lager/lagerzeile'
      7         PASSING t.xmldoc
      8         COLUMNS  pzn  NUMBER PATH 'pzn'
      9       ) l1_lager
     10  WHERE t.id = 1
     11  GROUP BY l1_lager.pzn
     12  ;
    
           PZN   COUNT(*)
    ---------- ----------
       1001094          1
       2487443      17745
       1218066          1
    
    Elapsed: 00:00:00.26
    
    Execution Plan
    ----------------------------------------------------------
    Plan hash value: 1955193779
    
    ----------------------------------------------------------------------------------------------
    | Id  | Operation              | Name                | Rows  | Bytes | Cost (%CPU)| Time     |
    ----------------------------------------------------------------------------------------------
    |   0 | SELECT STATEMENT       |                     | 17158 |  1055K|   243   (1)| 00:00:03 |
    |   1 |  HASH GROUP BY         |                     | 17158 |  1055K|   243   (1)| 00:00:03 |
    |*  2 |   HASH JOIN            |                     | 17158 |  1055K|   242   (1)| 00:00:03 |
    |   3 |    TABLE ACCESS FULL   | T_APOXML_LAGER      | 17157 |   335K|    68   (0)| 00:00:01 |
    |   4 |    MERGE JOIN CARTESIAN|                     | 18058 |   758K|   173   (0)| 00:00:03 |
    |*  5 |     TABLE ACCESS FULL  | T_APOXML            |     1 |    20 |     3   (0)| 00:00:01 |
    |   6 |     BUFFER SORT        |                     | 18058 |   405K|   170   (0)| 00:00:03 |
    |   7 |      TABLE ACCESS FULL | T_APOXML_LAGERZEILE | 18058 |   405K|   170   (0)| 00:00:03 |
    ----------------------------------------------------------------------------------------------
    
    Predicate Information (identified by operation id):
    ---------------------------------------------------
    
       2 - access("NESTED_TABLE_ID"="T"."SYS_NC0004100042$" AND
                  "NESTED_TABLE_ID"="SYS_ALIAS_3"."SYS_NC0000700008$")
       5 - filter("T"."ID"=1)
    
    Note
    -----
       - dynamic sampling used for this statement (level=2)
    

    Insofar as possible, always specify the full XPath (i.e. no axis down not as / /) and in the COLUMNS clause, use the data types of the real underlying columns.
    In this case:

    SQL> set autotrace traceonly
    SQL> SELECT l1_lager.StandVom
      2       , l2_lagerzeile.*
      3  FROM t_apoxml t
      4     , XMLTable(
      5         XMLNamespaces(default 'http://www.adas.de/spec/dws/v1'),
      6         '/adwsroot/lagerblock/lager'
      7         PASSING t.xmldoc
      8         COLUMNS
      9           StandVom                TIMESTAMP      PATH 'StandVom',
     10           lagerzeile              XMLTYPE        PATH 'lagerzeile'
     11       ) l1_lager
     12     , XMLTABLE(
     13         XMLNamespaces(default 'http://www.adas.de/spec/dws/v1'),
     14         '/lagerzeile'
     15         PASSING l1_lager.lagerzeile
     16         COLUMNS
     17           pzn                     NUMBER         PATH 'pzn',
     18           gtin                    VARCHAR2(4000) PATH 'gtin',
     19           artikelbezeichnung      VARCHAR2(200)  PATH 'name',
     20           menge                   VARCHAR2(28)   PATH 'menge',
     21           einheit                 VARCHAR2(8)    PATH 'einheit',
     22           ampreisvAmg             NUMBER(3)      PATH 'ampreisvAmg',
     23           ampreisvSgb             NUMBER(3)      PATH 'ampreisvSgb',
     24           btm                     NUMBER(3)      PATH 'btm',
     25           abdaWarengruppe         VARCHAR2(32)   PATH 'abdaWarengruppe',
     26           darreichungsform        VARCHAR2(12)   PATH 'darreichungsform',
     27           anbieter                NUMBER         PATH 'anbieter',
     28           lagertemperaturMin      NUMBER(10)     PATH 'lagertemperaturMin',
     29           lagertemperaturMax      NUMBER(10)     PATH 'lagertemperaturMax',
     30           notfalldepot            NUMBER(3)      PATH 'notfalldepot',
     31           abgaberegelung          VARCHAR2(80)   PATH 'abgaberegelung',
     32           artikelart              VARCHAR2(80)   PATH 'artikelart',
     33           mwstsatz                NUMBER(7)      PATH 'mwstsatz',
     34           listenEk                NUMBER(10)     PATH 'listenEk',
     35           listenVk                NUMBER(10)     PATH 'listenVk',
     36           notfalldepotEigen       VARCHAR2(1)    PATH 'notfalldepotEigen',
     37           anLager                 VARCHAR2(1)    PATH 'anLager',
     38           kalkulierterVk          NUMBER(10)     PATH 'kalkulierterVk',
     39           lagerort                VARCHAR2(320)  PATH 'lagerort',
     40           platzierung             VARCHAR2(80)   PATH 'platzierung',
     41           bestand                 NUMBER(10)     PATH 'bestand',
     42           fruehesterVerfall       TIMESTAMP      PATH 'fruehesterVerfall',
     43           bewirtschaftungssart    VARCHAR2(80)   PATH 'bewirtschaftungssart',
     44           nnek                    NUMBER(10)     PATH 'nnek'
     45       ) l2_lagerzeile
     46  WHERE t.id = 1
     47  ;
    
    17747 rows selected.
    
    Elapsed: 00:00:00.82
    
    Execution Plan
    ----------------------------------------------------------
    Plan hash value: 488593731
    
    ---------------------------------------------------------------------------------------------
    | Id  | Operation             | Name                | Rows  | Bytes | Cost (%CPU)| Time     |
    ---------------------------------------------------------------------------------------------
    |   0 | SELECT STATEMENT      |                     | 17158 |    42M|   242   (1)| 00:00:03 |
    |*  1 |  HASH JOIN            |                     | 17158 |    42M|   242   (1)| 00:00:03 |
    |   2 |   TABLE ACCESS FULL   | T_APOXML_LAGER      | 17157 |   552K|    68   (0)| 00:00:01 |
    |   3 |   MERGE JOIN CARTESIAN|                     | 18058 |    43M|   174   (1)| 00:00:03 |
    |*  4 |    TABLE ACCESS FULL  | T_APOXML            |     1 |    20 |     3   (0)| 00:00:01 |
    |   5 |    BUFFER SORT        |                     | 18058 |    43M|   171   (1)| 00:00:03 |
    |   6 |     TABLE ACCESS FULL | T_APOXML_LAGERZEILE | 18058 |    43M|   171   (1)| 00:00:03 |
    ---------------------------------------------------------------------------------------------
    
    Predicate Information (identified by operation id):
    ---------------------------------------------------
    
       1 - access("NESTED_TABLE_ID"="T"."SYS_NC0004100042$" AND
                  "SYS_ALIAS_5"."NESTED_TABLE_ID"="SYS_ALIAS_4"."SYS_NC0000700008$")
       4 - filter("T"."ID"=1)
    
    Note
    -----
       - dynamic sampling used for this statement (level=2)
    
    Statistics
    ----------------------------------------------------------
              0  recursive calls
              2  db block gets
            897  consistent gets
            886  physical reads
              0  redo size
         295154  bytes sent via SQL*Net to client
          13433  bytes received via SQL*Net from client
           1185  SQL*Net roundtrips to/from client
              1  sorts (memory)
              0  sorts (disk)
          17747  rows processed
    
  • Problem with the trigger...

    Hello world

    I created a trigger on a table that would be to insert the rows that are inserted, updated, or deleted in a new tracking table. But after creating the relaxation I tried adding a line and update of a column, but when I got an error message in SQL developer saying:

    2 errors, save the changes to the table "WLI_SCHEMA". "" PORTAL_CP_DETAILS ":
    Line 79: ORA-04098: trigger ' WLI_SCHEMA. TRACKER' is not valid and does not re-validation
    Line 80: ORA-04098: trigger ' WLI_SCHEMA. TRACKER' is not valid and does not re-validation
    ORA-06512: at line 1

    Could you please tell me what happened here?

    My trigger is defined as:

    CREATE or REPLACE trigger TRACKER
    After INSERT or UPDATE or DELETE on PORTAL_CP_DETAILS
    for each line
    BEGIN
    insert into PORTAL_CP_DETAILS_CHANGE_LOG (: NEW.) CP_NAME,: NEW. URL,: NEW. TEMP_ID,: NEW. PATHS,
    : NEW. MMD_PATH,: NEW. DPA_ID,: NEW. CERTIFICATE_EXPIRY_DATE,: NEW. ENVIRONMENT: NEW. EXPIRY_DAYS_LEFT, sysdate);

    Add one when your if ;)

    ...
    If the insertion
    SO -<-- you="" need="" a="">
    this_and_that;
    end if;
    ...

  • Help with a trigger

    Hello:

    I wrote the following trigger:

    CREATE OR REPLACE TRIGGER insACT

    AFTER INSERT ON ACT

    FOR EACH ROW

    BEGIN

    INSERT INTO ACT_VER

    ()Act_ID_N, Act_Ver_No_N, Act_Status_CD_C, Created_DT, Created_By_User_CD_C, Last_updated_DT, Updated_By_User_CD_C( )

    VALUES

    (:NEW. Act_ID_N, 1, :NEW. Act_Status_CD_C, :NEW. Created_DT, :NEW. Created_By_User_CD_C, :NEW. Last_updated_DT, :NEW. Updated_By_User_CD_C);

    END;

    This trigger compile with error. No idea what may be a problem with this trigger?


    Vincent


    Hello

    post the full error here.

    Select * from all_errors where name = 'INSACT ';

    Also provide scripts for tables.

    Only then can we give you better answers quickly.

  • I'm having a problem with the pictures on some pagies partially of fully duplacating other tiles nearby. Only occurs with Firefox.

    I'm having a problem with the photos on some pages partially to duplicate completely other tiles nearby. Only occurs with Firefox. The thumbnails are refreshed when I move the cursor over them, but again distort when you scroll the page. I have a few images, but cannot up-load them on this page of support for some reason any. Maybe I can email you if you need?

    Start Firefox in Safe Mode to check if one of the extensions (Firefox/tools > Modules > Extensions) or if hardware acceleration is the cause of the problem.

    • Put yourself in the DEFAULT theme: Firefox/tools > Modules > appearance
    • Do NOT click on the reset button on the startup window Mode safe

    You can check the preferences of network.http. * on the topic: config page and make sure that they have the default value.
    You can restore the default user set prefs ("BOLD") via the context menu.

  • problems with several hr2000 + external trigger mode

    I hope someone can me halp on this problem:

    I need to acquire spectra with two hr2000 + and a nirques256 with labview external trigger mode.

    The external trigger mode is done by another pc and also the train of pulpse generator.

    If a trigger after I'm going to generate a 100 impulse every 20ms for each device through a dedicted Council.

    If I only work with ghosts at times things works fine and the system is very stable, BUT if I work with two or three spectres by now I have a really strange (maybe for me) problem with the timeout.

    This is due to an incorrect number of pulses:

    If I work with two device then I need to produce pulses of 200 each 20ms but my spectrometers provide data every 40ms, but I need to equip every 20ms

    If I work with threedevice and then I need to produce pulses of 300 each 20ms but my spectrometers to obtain data each 60ms but I need to equip every 20ms

    Thus, in this way, I lose the synchronization of the three councils.

    An options may be to use a dedicated pc for each device

    I acquire the signal via usb and the problem is maybe duo to the bus

    I think maybe the problem is duo to the vi block! Maybe I can use single istance at times when I call the procedure

    Thank you

    I just solved the problem: it was a problem with reentrancy

    Default LabVIEW use not reentrant execution

  • Is there a problem with ValueChangeListener and af: table?

    Hello...

    I use JDeveloper 11.1.2.0.0

    Is there a problem with ValueChangeListener and af: table.

    Here my problem...

    I have two inputtext in af:table and I want to change the value of inputtext2 when I change the value of inputtext1
    so I put the autosubmit = "true" to inputtext1 and set the valuechangelistener method that is in the page bean
    and I put the partial inputtext2 trigger = "inputtext1 id".

    but when I run the page and change the value of inputtext1 that nothing happens.

    But if I have the previous scenario in af:panelFormLayout instead of af: table its work and the value of inputtext2 is changed to the user.

    any ideas...

    Thans.

    Sorry for the delay... :(

    And why if I use page JSF is the binding property disappears
    in the tab advanced in the property inspector.

    If you cannot power discovered the binding property in the palette of the means, your jsff page is automatically linked.
    If only the problem.

    try to create the new page jsff, while creating jsff, finally there is radio box something like
    do not expose the UI components automatically. check and create.

    and create a java file. Then you can bind components with the java file as you wish.

    to check your jsff page is autobinded are no means?
    Open your jsff page.

    Menu's that are on it - in this section. You can see the design menu that struck. If you hit it means you see Wizard property page go to the tab component binding
    There is a check box available

    If the box is ticked means that you page are automatically linked. If this isn't the case, you must link.

    -edited lately.

  • Problem with LOV Switcher

    11.1.1.2 ADF + ADF BC

    Hello

    I have a problem with the list of switch values, missing a piece of the puzzle

    In the object view I have:

    a notation attribute that has 2 lov defined for it - lov_a and lov_b
    a Type attribute which can have a value of 1,2,3,4 or 5
    a passenger attribure LovToUse which has the following expression: Type == 3? 'lov_a': 'lov_b '.

    In other words if the Type is 3 I would like lov_a to show otherwise, I want lov_b.

    I created an a jspx to edit and change the data in my view object.

    The attributes and the Type are on the jspx.
    Type is an autosubmit and side has a partial trigger on Type

    The idea is that when the user changes the Type via the user interface rating will change his lov depending on the Type.

    The problem I have is that when Type is changed to note without changing his lov because I guess the LovToUse attribute is not updated / refreshed.

    How to refresh LovToUse when Type is changed through the user interface and that is all I have to do to get note to use the correct lov?

    Concerning
    Paul

    You may forget to set the dependency of your attribute LovToUse.

    Check this box:
    http://adfpractice-Fedor.blogspot.com/2011/02/ADF-BC-multiple-lovs-for-Vos-attribute.html

  • Searchbar broken in v23 and problem with add - js related?

    Since the upgrade to v23, the search bar not working - I can enter search terms, but the menu drop-down appears on my second monitor, and pressing on enter, nothing happens - that is the search for the search bar no longer works, for any search engine installed.

    Also, even if it may seem unrelated question, I use the Devonthink added, in order to capture pages html since firefox directly to Devonthink Pro. After the capture of the page HTML in PAO, I can only convert a searchable PDF.
    Converting page captured from v23, in PAO, all I get is a reflection and a partial screenshot of the visible part of the original HTML page.

    These two functions worked perfectly in v22, but are broken to v23. I have since downgraded in v22, and both functions work as expected, so it is clearly a problem with Firefox v23.

    The only 'fixes' were either downgrade v22, or start with a new profile, v23.
    The search bar worked normally when booting in safemode, v23, but not when all THE modules, themes and extensions have been disabled.

    Whatever changes have been made in v23, required a new profile to 'fix' this problem.

    Again, reinstall all the extensions and try to put the same preferences is a way very frustrating to mitigate this kind of behavior of the software.

    Fortunately, it is often not necessary.

Maybe you are looking for