most unique separator between the key and the value.

Similar Questions

• Semi colon separated between the values

  Hello

  I have a table:

  CREATE TABLE TEST_A

  (

  ATT1 VARCHAR2 (10),

  ATT2 VARCHAR2 (10),

  ATT3 VARCHAR2 (10),

  ATT4 VARCHAR2 (10));

  
  

  INSERT INTO TEST_A

  VALUES (NULL, 'A', NULL, 'B');

  
  

  INSERT INTO TEST_A

  VALUES(,'D',,'E');

  
  

  COMMIT;

  
  

  I want that the output voltage: select * from test_a as:

  
  

  A; B

  D; E

  
  

  I want a semicolon separated between the values. If the first column has no value, it must not start with a separator semicolon.

  
  

  Thank you
  

  
  

  SELECT a.*,

  TRIM)

  BOTH

  ';'

  OF REGEXP_REPLACE)

  Att1 | ';' ||

  att2 | ';' ||

  att3 | ';' ||

  ATT4,

  ';+',

  ';'

  )

  ) att_list

  OF test_a one

  /

  ATT1 ATT2 ATT3 ATT4 ATT_LIST
  ---------- ---------- ---------- ---------- ----------
  A                     B          A; B
  D                     E          D; E
  A                                A

  SQL >

  SY.

• Separator between the left and right.

  The generated WebHelp has a separator (used to resize) which divides the left pane (TOC) in the right pane (main content). This separator has a border and therefore appears as a thick gray elevated line. I would like for the separator to a border and so it will appear as a thin gray line.
  
  The way to proceed is to specify frameborder = "0" in the < frame > tag to the right pane. However, if I change this in my start page (after generation), this frameborder = "0" is simply not applied do. Can someone tell me what I'm missing?
  
  Thank you
  K

  You get a free copy of the Skinny on skins of Rick Stone tutorial. It is essential for this kind of thing!

  Good luck
  Leon

• Difference of path between primary key and a Unique Index

  Hi all
  
  Is there a specific way the oracle optimizer to treat differently the Primary key and Unique index?
  
  Oracle Version

  SQL> select * from v$version;
  
  BANNER
  --------------------------------------------------------------------------------
  Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
  PL/SQL Release 11.2.0.3.0 - Production
  CORE    11.2.0.3.0      Production
  TNS for IBM/AIX RISC System/6000: Version 11.2.0.3.0 - Production
  NLSRTL Version 11.2.0.3.0 - Production
  
  SQL> 

  Sample data test for Index Normal
  

  SQL> create table t_test_tab(col1 number, col2 number, col3 varchar2(12));
  
  Table created.
  
  SQL> create sequence seq_t_test_tab start with 1 increment by 1 ;
  
  Sequence created.
  
  SQL>  insert into t_test_tab select seq_t_test_tab.nextval, round(dbms_random.value(1,999)) , 'B'||round(dbms_random.value(1,50))||'A' from dual connect by level < 100000;
  
  99999 rows created.
  
  SQL> commit;
  
  Commit complete.
  
  SQL> exec dbms_stats.gather_table_stats(USER_OWNER','T_TEST_TAB',cascade => true);
  
  PL/SQL procedure successfully completed.
  
  SQL> select col1 from t_test_tab;
  
  99999 rows selected.
  
  
  Execution Plan
  ----------------------------------------------------------
  Plan hash value: 1565504962
  
  --------------------------------------------------------------------------------
  | Id  | Operation         | Name       | Rows  | Bytes | Cost (%CPU)| Time     |
  --------------------------------------------------------------------------------
  |   0 | SELECT STATEMENT  |            | 99999 |   488K|    74   (3)| 00:00:01 |
  |   1 |  TABLE ACCESS FULL| T_TEST_TAB | 99999 |   488K|    74   (3)| 00:00:01 |
  --------------------------------------------------------------------------------
  
  
  Statistics
  ----------------------------------------------------------
            1  recursive calls
            0  db block gets
         6915  consistent gets
          259  physical reads
            0  redo size
      1829388  bytes sent via SQL*Net to client
        73850  bytes received via SQL*Net from client
         6668  SQL*Net roundtrips to/from client
            0  sorts (memory)
            0  sorts (disk)
        99999  rows processed
  
  SQL> create index idx_t_test_tab on t_test_tab(col1);
  
  Index created.
  
  SQL> exec dbms_stats.gather_table_stats('USER_OWNER','T_TEST_TAB',cascade => true); 
  
  PL/SQL procedure successfully completed.
  
  SQL> select col1 from t_test_tab;
  
  99999 rows selected.
  
  
  Execution Plan
  ----------------------------------------------------------
  Plan hash value: 1565504962
  
  --------------------------------------------------------------------------------
  | Id  | Operation         | Name       | Rows  | Bytes | Cost (%CPU)| Time     |
  --------------------------------------------------------------------------------
  |   0 | SELECT STATEMENT  |            | 99999 |   488K|    74   (3)| 00:00:01 |
  |   1 |  TABLE ACCESS FULL| T_TEST_TAB | 99999 |   488K|    74   (3)| 00:00:01 |
  --------------------------------------------------------------------------------
  
  
  Statistics
  ----------------------------------------------------------
            1  recursive calls
            0  db block gets
         6915  consistent gets
            0  physical reads
            0  redo size
      1829388  bytes sent via SQL*Net to client
        73850  bytes received via SQL*Net from client
         6668  SQL*Net roundtrips to/from client
            0  sorts (memory)
            0  sorts (disk)
        99999  rows processed
  
  SQL> 

  Examples of test when using primary key data
  

  SQL> create table t_test_tab1(col1 number, col2 number, col3 varchar2(12));
  
  Table created.
  
  SQL> create sequence seq_t_test_tab1 start with 1 increment by 1 ;
  
  Sequence created.
  
  SQL> insert into t_test_tab1 select seq_t_test_tab1.nextval, round(dbms_random.value(1,999)) , 'B'||round(dbms_random.value(1,50))||'A' from dual connect by level < 100000;
   
  99999 rows created.
  
  SQL> commit;
  
  Commit complete.
  
  SQL> exec dbms_stats.gather_table_stats('USER_OWNER','T_TEST_TAB1',cascade => true);
  
  PL/SQL procedure successfully completed.
  
  SQL> select col1 from t_test_tab1;
  
  99999 rows selected.
  
  
  Execution Plan
  ----------------------------------------------------------
  Plan hash value: 1727568366
  
  ---------------------------------------------------------------------------------
  | Id  | Operation         | Name        | Rows  | Bytes | Cost (%CPU)| Time     |
  ---------------------------------------------------------------------------------
  |   0 | SELECT STATEMENT  |             | 99999 |   488K|    74   (3)| 00:00:01 |
  |   1 |  TABLE ACCESS FULL| T_TEST_TAB1 | 99999 |   488K|    74   (3)| 00:00:01 |
  ---------------------------------------------------------------------------------
  
  
  Statistics
  ----------------------------------------------------------
            1  recursive calls
            0  db block gets
         6915  consistent gets
            0  physical reads
            0  redo size
      1829388  bytes sent via SQL*Net to client
        73850  bytes received via SQL*Net from client
         6668  SQL*Net roundtrips to/from client
            0  sorts (memory)
            0  sorts (disk)
        99999  rows processed
  
  SQL> alter table t_test_tab1 add constraint pk_t_test_tab1 primary key (col1);
  
  Table altered.
  
  SQL> exec dbms_stats.gather_table_stats('USER_OWNER','T_TEST_TAB1',cascade => true); 
  
  PL/SQL procedure successfully completed.
  
  SQL> select col1 from t_test_tab1;
  
  99999 rows selected.
  
  
  Execution Plan
  ----------------------------------------------------------
  Plan hash value: 2995826579
  
  ---------------------------------------------------------------------------------------
  | Id  | Operation            | Name           | Rows  | Bytes | Cost (%CPU)| Time     |
  ---------------------------------------------------------------------------------------
  |   0 | SELECT STATEMENT     |                | 99999 |   488K|    59   (2)| 00:00:01 |
  |   1 |  INDEX FAST FULL SCAN| PK_T_TEST_TAB1 | 99999 |   488K|    59   (2)| 00:00:01 |
  ---------------------------------------------------------------------------------------
  
  
  Statistics
  ----------------------------------------------------------
            1  recursive calls
            0  db block gets
         6867  consistent gets
            0  physical reads
            0  redo size
      1829388  bytes sent via SQL*Net to client
        73850  bytes received via SQL*Net from client
         6668  SQL*Net roundtrips to/from client
            0  sorts (memory)
            0  sorts (disk)
        99999  rows processed
  
  SQL> 

  If you see here the same even as the statistics were gathered,
  * In the 1st table T_TEST_TAB, table always use FULL table access after creating indexes.
  * And in the 2nd table T_TEST_TAB1, table uses PRIMARY KEY as expected.
  
  Any comments?
  
  Kind regards
  BPat

  >
  * In the 1st table T_TEST_TAB, table always use FULL table access after creating indexes.
  * And in the 2nd table T_TEST_TAB1, table uses PRIMARY KEY as expected.
  >
  Yes - for the first table a full table scan will be used as the currently selected column is nullable and indexes do not include null values.

  The index can be used for the second query, since all the data (first column) is available between the index and there may be no NULL values because of the primary key. If you check constraints, you find that the there is now a CHECK constraint to ensure that the first column cannot be null.

  For a full and interesting discussion see the explanation of this and a related issue on the question I ask in this thread
  What SYS tables (not seen) contain the value NULL spec /not/ column definition? and my response he posted: 23 April 2012 09:02

  I ask the question is based on a question here which is similar to yours
  Columns becoming nullable after a fall of primary key?

• composite unique constraint on the values of parent and child?

  Is it possible to have a composite unique constraint that contains the values of the child elements? The example below has the "child" elements are offline, but it's preferred, but optional, I know that you can have a unique constraint in the set of tables without using a reference table that contains the constraint and the two columns. How xdb manages this requirement?
  
  permit:

  <parent ID="1">
     <child><name>test1</name></child>
     <child><name>test2</name></child>
  </parent>
  <parent ID="2">
     <child><name>test1</name></child>
     <child><name>test2</name></child>
  </parent>

  not allowed:

  <parent ID="1">
     <child><name>test1</name></child>
     <child><name>test1</name></child>
  </parent>

  <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" 
             xmlns:xdb="http://xmlns.oracle.com/xdb"
             xdb:storeVarrayAsTable="true"
             elementFormDefault="qualified">
      
      <xs:element name="parent" type="Parent_T"
          xdb:columnProps="CONSTRAINT parent_pkey PRIMARY KEY (XMLDATA.ID)"
          xdb:defaultTable="PARENT"/>
  
      <xs:complexType name="Parent_T" xdb:SQLType="PARENT_T" xdb:maintainDOM="false">
          <xs:sequence>
              <xs:element name="child" type="Child_T" minOccurs="1" maxOccurs="unbounded" xdb:SQLName="CHILD"
                        xdb:SQLInline="false" xdb:defaultTable="CHILD" "/>
          </xs:sequence>
          <xs:attribute name="ID" xdb:SQLName="ID" use="required" />
      </xs:complexType>
      
      <xs:complexType name="Child_T" xdb:SQLType="CHILD_T">
         <xs:sequence>
           <xs:element name="name" type="xs:string" xdb:SQLName="NAME"/>
         </xs:sequence>
       </xs:complexType>     
  </xs:schema>

  xdb:columnProps = "CONSTRAINT parent_pkey PRIMARY KEY (XMLDATA.ID), * UNIQUE (XMLDATA.» "Child.Name) *" triggers the non-existent attribute
  
  
  A possible solution would be to copy the value of the primary key parent of the child element, then I could create a composite unique constraint using only the values of the child. However, I have this same requirement elsewhere in my lowest nested schema, and it can become messy / bad design with cascading of all primary keys on the schema. For example, I have a recursive element in which two attributes must be unique only within the parent company:

  <parent id="1">
     <child a="1" b="1">
        <child a="1" b="2">
           <child a="1" b="1" /> *not allowed
        </child>
     </child>
     <child a="1" b="2" /> *not allowed
  </parent>

  Possible solution:

  <child a="1" b="2" parent_id="1" />
  <xs:complexType name="Child_T>
     <xs:sequence>
        <xs:element name="child" xsd:SQLInline="false" xsd:columnProps="UNIQUE(XMLDATA.a,XMLDATA.b,XMLDATA.parent_id)" minOccurs="0" maxOccurs="unbounded" type="Child_T">
     </xs:sequence>
     </xs:element
  </xs:complexType>

  Is there a better design?
  
  

  Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi 
  PL/SQL Release 10.2.0.4.0 - Production                           
  CORE     10.2.0.4.0     Production                                       
  TNS for Linux: Version 10.2.0.4.0 - Production                   
  NLSRTL Version 10.2.0.4.0 - Production 

  You can do something like this:

  SQL> DECLARE
    2
    3    xsd_doc xmltype := xmltype('
    4  
    5    
    6      
    7        
    8          
    9        
   10      
   11    
   12    
   13      
   14        
   15          
   16        
   17      
   18    
   19    
   20      
   21        
   22          
   23        
   24        
   25      
   26    
   27    
   28      
   29        
   30          
   31        
   32      
   33    
   34  ');
   35
   36  BEGIN
   37
   38    dbms_xmlschema.registerSchema(
   39      schemaURL => 'test_parent.xsd',
   40      schemaDoc => xsd_doc,
   41      local => true,
   42      genTypes => true,
   43      genbean => false,
   44      genTables => false,
   45      enableHierarchy => dbms_xmlschema.ENABLE_HIERARCHY_NONE
   46    );
   47
   48  END;
   49  /
  
  PL/SQL procedure successfully completed
  
  SQL> CREATE TABLE my_xml_table OF XMLTYPE
    2  XMLTYPE STORE AS OBJECT RELATIONAL
    3  XMLSCHEMA "test_parent.xsd"
    4  ELEMENT "root"
    5  VARRAY xmldata."parent" STORE AS TABLE my_parent_tab
    6  (
    7    VARRAY "child" STORE AS TABLE my_child_tab
    8  )
    9  ;
  
  Table created
  
  SQL> ALTER TABLE my_parent_tab ADD CONSTRAINT parent_uk UNIQUE (nested_table_id, "ID");
  
  Table altered
  
  SQL> ALTER TABLE my_child_tab ADD CONSTRAINT child_uk UNIQUE (nested_table_id, "name");
  
  Table altered
   
  

  Then:

  SQL> insert into my_xml_table values (
    2  xmltype('
    3     test1
    4     test2
    5  
    6  
    7     test1
    8     test2
    9  ')
   10  );
  insert into my_xml_table values (
  *
  ERREUR à la ligne 1 :
  ORA-00001: violation de contrainte unique (DEV.PARENT_UK)
  
  SQL> insert into my_xml_table values (
    2  xmltype('
    3     test1
    4     test1
    5  
    6  
    7     test1
    8     test2
    9  ')
   10  );
  insert into my_xml_table values (
  *
  ERREUR à la ligne 1 :
  ORA-00001: violation de contrainte unique (DEV.CHILD_UK)
  
  SQL> insert into my_xml_table values (
    2  xmltype('
    3     test1
    4     test2
    5  
    6  
    7     test1
    8     test2
    9  ')
   10  );
  
  1 ligne créée.
  

  http://download.Oracle.com/docs/CD/B19306_01/AppDev.102/b14259/xdb06stt.htm#sthref987

• Column of child binding between the values of the parent record

  I know it is not a declarative constraint to do, but I wonder what ideas have for the best model to use.
  
  I have a table parent ALPHA with columns ALPHA_ID, start_date and end_date.
  Then I have a BETA child table with columns BETA_ID, ALPHA_ID, and TRAN_DATE.
  
  I would like to limit this BETA. TRAN_DATE is located between ALPHA. Start_date and ALPHA. End_date I hesitate to use a trigger because BETA will be many inserts.
  
  I looked at the creation of an ALPHA_DATE table with the columns TRAN_DATE, ALPHA_ID, start_date and end_date, with the first three columns as foreign key the same columns in ALPHA, and a CHECK constraint that (TRAN_DATE between start_date and end_date), then leave BETA (ALPHA_ID, TRAN_DATE) be a foreign key for ALPHA_DATE (ALPHA_ID TRAN_DATE).
  
  Thank you
  Matt

  Personally I would generate just triggers for it. And see if the drop in performance may be taken.

  Of course, in Oracle14 (or more?) you can do:

  create assertion alpha_beta_date_constraint
  check(not exists
  (select 'tuple in this join'
   from alpha a
       ,beta b
   where a.alpha_id = b.alpha_id
      and not (b.tran_date between a.start_date and a.end_date)
  ))
  /
  

  You can also use the infamous thing materialized view.
  -Create a MV that's bassically by using the query above to search for the faulty lines.
  -Add a check on this MV constraint which is always false (for example, check (0 = 1)).
  -Do a refresh on the validation of MV type.

• Updated between the values

  Hello

  Could someone help me with a very trivial problem.

  I have after the update clause, but it gives the error ORA-01427. Seems that it is between the two problem. How should I change what he begins to work?

  Update sales_in

  the value of sale = (select a.sales in the sales_out one

  where a.sales_year_month between 201501 and 201505);

  Update sales_in I

  the value of sale = (select a.sales in the sales_out one

  where a.sales_year_month = i.sales_year_month

  )

  where i.sales_year_month between 201501 and 201505;

• Spaces between the values in the output

  Hi all
  
  I have a doubt, this is the scenario in the report.
  
  Try to display the names of channel which is a special category in the bottom of the report. The names are identified by the DESCR field in the <? FIELD? > tag, starting with a. (ex: A-SONY).
  But there are some other channels to come between the two, as the commercial channels. Comes it like that.
  <? FIELD? >
  <? DESCR? > A-SONY <? / DESCR? >
  <? / FIELD? >
  <? FIELD? >
  <? DESCR? > B-SPORTS <? / DESCR? >
  <? / FIELD? >
  <? FIELD? >
  <? DESCR? > A-STAR <? / DESCR? >
  <? / FIELD? >
  
  Now, when we display these values, it displays properly, but leaving a space between them, because it has other values in the meantime.
  Can we avoid this space?, this creates some alignment problems.
  
  Thanks in advance,
  Imtiaz.

  You can do it like below, so that it picks up the values beginning with 'A' alone

• REGEXP_REPLACE - Exclude ONLY zeros if there is between a character and numeric value [1-9]

  Hi all

  I need your help in providing me the regular expression to exclude zeros only if it sits between the characters and a nonzero numerical value.

  For example:

  PL032 = > PL32

  GDP500 = > GDP500 (should remain is that the zeros are not between a character and not null)

  SOA008 = > SOA8

  GDP000 = > GDP0 (only exception: If that's all the 000 and then convert it 0)

  Thank you for your help in advance.

  Kind regards

  Emeline

  Hi, emeline,

  1000877 wrote:

  Hi all

  I need your help in providing me the regular expression to exclude zeros only if it sits between the characters and a nonzero numerical value.

  For example:

  -ONLINE PL32 PL032

  GDP500-online GDP500 (expected to remain is that the zeros are not between a character and not null)

  SOA008-ONLINE SOA8

  GDP000 => GDP0 (only exception: If that's all the 000 and then convert it 0)

  Are characters.  When you say "between characters and numeric value", do you mean "between non-numeric characters and numeric characters?

  If so:

  REGEXP_REPLACE (str,

  '(\D)0+(\d)'

  , « \1\2 »

  )

  \D (with a capital D) means any non-digit character.

  \d (with a small d) means any numeric characters, including 0.  Because regular expressions are greedy by default, "0 + 'match all ' 0' if some other number follows, but leave the last '0' (as you want) then there is not another number immediately after him."

• SQL Native Performance difference between coded hard and parameter value

  Hello
  
  I have a SQL query (Oracle) native (quite long and complex with many subqueries) which returns in less than a second in ODSI and using an external SQL tool. This query contains a hardcoded for a particular, namely column value, a date column.
  When I change the function ODSI signature so that I have pass a parameter, and then replace the hardcoded value in the native SQL with the appropriate parameter binding notation (i.e. '?'), the query takes much longer (2-30 seconds). The duration of the query depends on how many records is returned, so he must execute a separate query for each of the outcomes (i.e. most returned results, longer the query takes to return).
  What can I do to maintain the duration of my low ODSI request while allowing the setting?

  Thank you. Try the oracle.jdbc.OracleDriver in WLS/ODSI, let know us.

• What is the difference between primary key and unique indexes with forced not null?

  Primary key is = unique index + not null?

  The short answer is Yes.

  However, even if the primary key, applying both uniquness and not null, there is a notion of "special".

  You can only have one primary key in tables, but you can have multiple unique indexes and constraints not null.

  See: https://asktom.oracle.com/pls/asktom/f?p=100:11:0:P11_QUESTION_ID:8743855576462

• Adjustment of separation between the notes

  How to adjust the spacing between Notes Pages 5.6?

  P.S. This question seems to be recurring much in this forum. In the past, it was thanks to a non-intuitive location of the setting in the settings of 'Document '. Recently, it's because he disappeared from there...

  The ability to separate the reference entries according to a value specified in Pages v5 has not disappeared.

  

• Unique constraint on the values in both directions

  I'm looking to create a unique constraint that works in two ways. Say I got a constraint unique in columns 1 and 2. I want it to be impossible for the two lines below the two exist at the same time. Is there a way to do this? I googled around for a while now and I found nothing that works so far.

  Header 1	Header 2
  Dog	CAT
  CAT	Dog

  Hello

  You can create an index based on a single function:, like this:

  CREATE UNIQUE INDEX table_x_header_1_header_2

  ON table_x (LESS (header_1, header_2)

  More LARGE (header_1, header_2)

  );

  How will you use these values?  You might be better to simply create a regular old unique constraint, but also have a CHECK constraint to ensure that header_1<= header_2. ="" that="" way,="" when="" you="" want="" to="" search="" for="" the="" combination="" ('cat',="" 'dog')="" you="" won't="" have="" to="" search="" for="" ('dog',="" 'cat')="">

• difference between the values in the adjacent table.

  Hello

  I want to subtract from the adjacent elements in a table. I mean 1 element element-2e, 2-3, 3-4, 4-5 and so on... I HAV searchd for array index handling rem. but dint get... Help me. Thanks in advance

  Hi n,

  as easy as this:

  

• Problem of correspondence between the values in a table

  I have a table of product
  
  Qty of level type ID Grp
  ABC 101 1 1 100
  101 80 1 2 ABC
  101 3 1 65 ABC
  ABC 101 1 2 45
  ABC 101 2 2 100
  101 3 2 10 ABC
  
  Here, I need to check if the level (id.grp), type = 2 present in type 1 and type 2 = quantity is greater than 40% of the quantity of type = 1
  
  Finally, we should get
  
  Qty of level type ID Grp
  ABC 101 1 2 45 (more than 40% of 100)
  ABC 101 2 2 100 (more than 40% of 80)
  
  Please help me
  
  Thanks in advance

  SELECT *
    FROM product p1
   WHERE p1.TYPE = 2
     AND p1.qty > (SELECT MIN (p2.qty * 40 / 100)
                     FROM product p2
                    WHERE p1.id = p2.id
                      AND p1.grp = p2.grp
                      AND p1.level_ = p2.level_
                      AND p2.TYPE = 1
                  )
  

  Kind regards
  Vijay

  Published by: Vijaya Sekhar Reddy P on November 18, 2009 18:03
  Changed MAX and MIN