Sometimes we have to elaborate rows- results of a SELECT- in a way we cannot think to accomplish it with simple SQL code but we can be wrong ... SQL is pretty powerful. Let's take this case.
What we have:
| Customer | Wishlist |
| Customer 1 | AA11, BB22, FF92 |
| Customer 2 | CC43, RR55 |
What we need:
| Customer | Wished product |
| Customer 1 | AA11 |
| Customer 1 | BB22 |
| Customer 1 | FF92 |
| Customer 2 | CC43 |
| Customer 2 | RR55 |
If you are working with Oracle and jdbc API and you are facing an odd behaviour trying to fetch the value of a CLOB or BLOB field, the following note could help you.
Making a SELECT includes the fetch of one or more CLOBs the system can returns a value like "oracle.sql.CLOB@...." instead of the real value of the field. It seems the buffer cannot handle a so big and memory expensive value. A workaround is to use an Oracle function converts the CLOB in a VARCHAR and trim the value as requested.
