Recent changes to Home

Home modified by Michael

Michael — Fri, 29 Jun 2018 11:16:04 -0000

--- v36
+++ v37
@@ -13,7 +13,7 @@
 * SYS.DBMS_LOB 
 * SYS.UTL_I18N

-By default, this privileges are already granted to PUBLIC so it may not be necessary to grant them explicitly.
+By default, these privileges are already granted to PUBLIC so it may not be necessary to grant them explicitly.

 Components
 ---

Home modified by Michael

Michael — Wed, 27 Jun 2018 11:45:56 -0000

--- v35
+++ v36
@@ -39,7 +39,7 @@
     * with a row separator, or
     * with a fixed row width (in characters)

-The "separatedcolumns" and "fixedcolumns" functions are overloaded for CLOBs, BLOBs, BFILEs and VARCHAR2s as data sources.
+The separatedcolumns and fixedcolumns functions are overloaded for CLOBs, BLOBs, BFILEs and VARCHAR2s as data sources.
 For binary data sources (like BLOBs or BFILEs) you should specify the correct character set. If you do not do this, LOB2Table will assume that the data is encoded with the database character set.
 LOB2Table will automatically ignore (i.e. remove) any Byte Order Mark (aka BOM or Unicode character U+FEFF) at the beginning of LOBs or VARCHAR2s.
 For details about the provided functions take a look at the package specification.

Home modified by Michael

Michael — Wed, 27 Jun 2018 11:42:30 -0000

--- v34
+++ v35
@@ -13,7 +13,7 @@
 * SYS.DBMS_LOB 
 * SYS.UTL_I18N

-By default, this privilege is already granted to PUBLIC so it may not be necessary to grant it explicitly.
+By default, this privileges are already granted to PUBLIC so it may not be necessary to grant them explicitly.

 Components
 ---

Home modified by Michael

Michael — Wed, 27 Jun 2018 10:59:18 -0000

--- v33
+++ v34
@@ -8,7 +8,12 @@
 * CREATE TYPE
 * CREATE PROCEDURE

-Additionally the EXECUTE object privilege on the package SYS.DBMS_LOB is required. By default, this privilege is already granted to PUBLIC so it may not be necessary to grant it explicitly.
+Additionally the EXECUTE object privilege on the following packages is required:
+
+* SYS.DBMS_LOB 
+* SYS.UTL_I18N
+
+By default, this privilege is already granted to PUBLIC so it may not be necessary to grant it explicitly.

 Components
 ---

Home modified by Michael

Michael — Sat, 23 Jun 2018 12:04:03 -0000

--- v32
+++ v33
@@ -36,6 +36,7 @@

 The "separatedcolumns" and "fixedcolumns" functions are overloaded for CLOBs, BLOBs, BFILEs and VARCHAR2s as data sources.
 For binary data sources (like BLOBs or BFILEs) you should specify the correct character set. If you do not do this, LOB2Table will assume that the data is encoded with the database character set.
+LOB2Table will automatically ignore (i.e. remove) any Byte Order Mark (aka BOM or Unicode character U+FEFF) at the beginning of LOBs or VARCHAR2s.
 For details about the provided functions take a look at the package specification.

 Examples

Home modified by Michael

Michael — Fri, 01 Sep 2017 09:41:57 -0000

--- v31
+++ v32
@@ -168,7 +168,7 @@
 ---
 Because of some SQL and PL/SQL restrictions in Oracle there are two limitations of LOB2Table:

-* A data row inside the LOBs cannot consists of more than 32767 bytes.
+* A data row inside the LOBs cannot consist of more than 32767 bytes.
 If a larger row is encountered then the exception row_error is thrown. There is currently no way to evade this restriction.
 * A data column cannot consist of more than 4000 bytes.
 If a larger column is encountered then the exception column_error is thrown.

Home modified by Michael

Michael — Fri, 01 Sep 2017 09:39:47 -0000

--- v30
+++ v31
@@ -32,10 +32,10 @@
 * Separated columns (by using the "separatedcolumns" function)
 * Fixed columns (by using the "fixedcolumns" function)
     * with a row separator, or
-    * with a fixed row with (in characters)
+    * with a fixed row width (in characters)

 The "separatedcolumns" and "fixedcolumns" functions are overloaded for CLOBs, BLOBs, BFILEs and VARCHAR2s as data sources.
-For binary data sources (like BLOBs or BFILEs) you should specify the correct character set. If you do not do this LOB2Table will assume that the data is encoded with the database character set.
+For binary data sources (like BLOBs or BFILEs) you should specify the correct character set. If you do not do this, LOB2Table will assume that the data is encoded with the database character set.
 For details about the provided functions take a look at the package specification.

 Examples

Home modified by Michael

Michael — Thu, 19 May 2016 08:20:49 -0000

--- v29
+++ v30
@@ -23,7 +23,7 @@

 You use the various functions that the package lob2table provides to get the CSV or fixed column data from LOBs as tables.

-For every function in lob2table there is a "sibling" function with a "2"-suffix that return the same data in a non-pipelined way. This simplifies usage in pure PL/SQL code.
+For every function in lob2table there is a "sibling" function with a "2"-suffix that returns the same data in a non-pipelined way. This simplifies usage in pure PL/SQL code.

 Usage
 ---
@@ -34,7 +34,7 @@
     * with a row separator, or
     * with a fixed row with (in characters)

-The "separatedcolumns" and "fixedcolumns" functions are overloaded for CLOBs, BLOBs or BFILEs as data source.
+The "separatedcolumns" and "fixedcolumns" functions are overloaded for CLOBs, BLOBs, BFILEs and VARCHAR2s as data sources.
 For binary data sources (like BLOBs or BFILEs) you should specify the correct character set. If you do not do this LOB2Table will assume that the data is encoded with the database character set.
 For details about the provided functions take a look at the package specification.

Home modified by Michael

Michael — Sat, 02 Jan 2016 11:10:59 -0000

--- v28
+++ v29
@@ -84,9 +84,9 @@

 | DEPTNO | DNAME | ROW_NO | COLUMN1 | COLUMN2 | COLUMN3 | COLUMN4 |
 | ------ | ------ | ------ | ------ | ------ | ------ | ------ |
-| 10 | ACCOUNTING | 1 | 1234567890 | Data | 12.3 |
-| 10 | ACCOUNTING | 2 | 0987654321 | Sampe 1, started | 9.5 |
-| 10 | ACCOUNTING | 3 | 456 | Test"1" | 7 |
+| 10 | ACCOUNTING | 1 | 1234567890 | Data | 12.3 | *(null)* |
+| 10 | ACCOUNTING | 2 | 0987654321 | Sampe 1, started | 9.5 | *(null)* |
+| 10 | ACCOUNTING | 3 | 456 | Test"1" | 7 | *(null)* |

 Also an outer join logic is possible:

@@ -107,10 +107,10 @@

 | DEPTNO | DNAME | ROW_NO | COLUMN1 | COLUMN2 | COLUMN3 | COLUMN4 |
 | ------ | ------ | ------ | ------ | ------ | ------ | ------ |
-| 10 | ACCOUNTING | 1 | 1234567890 | Data | 12.3 |
-| 10 | ACCOUNTING | 2 | 0987654321 | Sampe 1, started | 9.5 |
-| 10 | ACCOUNTING | 3 | 456 | Test"1" | 7 |
-| 40 | OPERATIONS |
+| 10 | ACCOUNTING | 1 | 1234567890 | Data | 12.3 | *(null)* |
+| 10 | ACCOUNTING | 2 | 0987654321 | Sampe 1, started | 9.5 | *(null)* |
+| 10 | ACCOUNTING | 3 | 456 | Test"1" | 7 | *(null)* |
+| 40 | OPERATIONS | *(null)* | *(null)* | *(null)* | *(null)* | *(null)* |

 Let's query the fixed column width data:

@@ -132,8 +132,8 @@

 | DEPTNO | DNAME | ROW_NO | COLUMN1 | COLUMN2 | COLUMN3 | COLUMN4 |
 | ------ | ------ | ------ | ------ | ------ | ------ | ------ |
-| 20 | RESEARCH | 1 | 12345 | Data1•• | 321 |  |
-| 20 | RESEARCH | 2 | 123•• | Data321 | 12 |  |
+| 20 | RESEARCH | 1 | 12345 | Data1•• | 321 | *(null)* |
+| 20 | RESEARCH | 2 | 123•• | Data321 | 12 | *(null)* |

 Note here the trailing spaces (denoted as •) - LOB2Table does not trim them. It's up to you, the developer, to decide if, how and when you want to trim them away.

Home modified by Michael

Michael — Fri, 01 Jan 2016 17:16:02 -0000

--- v27
+++ v28
@@ -56,7 +56,7 @@
 | 30 | SALES | CHICAGO | 123456ABCDEF789XYZ654321GHIJ••987ZXY123456ABCDEF78•XYZ |
 | 40 | OPERATIONS | BOSTON | *(null)* |

-As you may know this is the famous DEPT table of the SCOTT schema where I added a CLOB column named "MYCLOB". Note that - for clarity - space in the MYCLOB column are denoted as bulls (•).
+As you may know this is the famous DEPT table of the SCOTT schema where I added a CLOB column named "MYCLOB". Note that - for clarity - spaces in the MYCLOB column are denoted as bulls (•).
 Consider the content of the MYCLOB column:

 * The row with DEPTNO = 10 contains separated data where the row separator is the new line character (↵), i.e. chr(10), and the column separator is the comma character. Additionally, as the (optional) text delimiter the double-quote character is used.