Tag Info

New answers tagged

0

You mention you have tried SQL*Plus and Toad; what is your client operating system, Windows? Unix? See NLS_OS_CHARSET Environment Variable that is an environment variable set on your client to a value that your client understands and supports. If you are on Unix, invoke the locale command and see what LANG or LC_ALL is set to; you may need to set ...


1

The chinese characters are decoded correctly with utl_i18n.unescape_reference. In fact they just aren't displayed properly in your query result which might not support those special characters. You can confirm that with this SQL Fiddle. It is the client which is respsonsible to display the characters appropriately. If the client can not display a ...


1

You might have wanted this: WITH XML_DATA AS (SELECT XMLTYPE('<?xml version="1.0" encoding="UTF-8"?> <response> <phone> <number>859111</number> <contactModes> <mode>AUTO_DIAL</mode> <mode>AUTO_TEXT</mode> <mode>MANUAL_DIAL</mode> ...


0

I found the answer myself after reading through loads of documentation from Oracle. The answer comes in two parts. First, my original question can be solved by using XMLTable: SELECT x.ID AS "MEASUREMENT_ID", x.GUID AS "MEASUREMENT_GUID", a.COLUMN_VALUE AS "MESSAGE" FROM SPERF_XML_RAW x, ...


0

I was able to automate the process enough, keyword being enough. To help anyone else dealing with exporting from Microsoft Access and importing to PostgreSQL I'm providing details that helped us work through the errors we encountered. While I'm fairly competent with MySQL and new (though still reasonably well at PostgreSQL) the people who setup the various ...



Top 50 recent answers are included