Over the past several months, I have been amending TDP’s Teradata syntax XML as there were some reserved words not included in the original file. Also, I have modified the ODBC XML to include Teradata’s key words as I still use the ODBC connection while upcoming features for the .Net connection are being developed.
I am attaching the files for those that work in Teradata and would like to replace their syntax XMLs as well. As I make improvements, I will update this post. The files go in the install directory under Templates\Languages (Windows).
While they are only syntax highlighting XMLs… It is highly recommended that you make a backup copy of your existing files if you decide to try them out. I take no responsibility for damage caused to your system(s) by replacing these files with my copies.
Language.SQL.Odbc.xml (24.6 KB)
Language.SQL.Teradata.xml (24 KB)
Teradata drivers support a text-based format for XML values. A client application or driver that uses the text format might require access to an XML parser to be able to parse the XML received on the wire.
The text format returns the XML serialization of the XML value. XML values retrieved in the text format are encoded in UTF-8. The following shows an example of document retrieval.
<?xml version="1.0" encoding="UTF-8"?>
<Address>100 1st Street One City, CA 12345</Address>
<order Number="NW-01-16366" Date="Feb/28/2001">
<ShipTo>Widgets Inc., 123 Regency Parkway, Portland, OR 43211</ShipTo>
For the text format, the server will not try to pretty-print the XML value when serializing it for transfer to the client. If the client application needs to display the XML, it is up to the application to decide whether to do pretty-printing, provide syntax-highlighting, or other display options.