Teradata’s latest and greatest Eclipse offering has been released and is available in the Teradata Developer Exchange download section (Teradata Plug-in for Eclipse) . The 13.11.00 release builds on the 13.10.00 offering by boasting increased functionality.
Passwords can expire. In many cases the original password is a temporary password and the user is expected to change it when logging on for the first time. It is now recognized when a password expires (SQL Warning error code: 3032) and the user is prompted for the new password. The connection is retried with the JDBC property ‘NEW_PASSWORD’ set to the new password and the new password is saved in the profile.
The iBatis CRUD Wizard provides a wizard that generates the SQL and iBatis code for all of the CRUD operations (create, read, update, and delete) for a selected database table. The generated iBatis SQL map can then be used to create a Web Service or used to create a Java application that uses the iBatis framework. It provides users with a quick and easy way to create an application that can do basic operations on a Teradata database table.
The iBatis View Web Service Wizard provides a wizard that creates a Web Service from a Teradata View. The new wizard generates SQL select statements on the View. The SQL statements are then put in an iBatis SQL Map. Once this is done, a Web Service is created from the new iBatis SQL Map.
The iBatis DAO Web Services Wizard has added support for returning OUT parameters from a Web Service. The wizard returns the Mapped Parameter class as a response for the generated Web Service.
This feature provides the ability to export and import the history information from the Teradata SQL History to an external file. This ability allows SQL statements, which are part of the SQL History, to be shared between installations of Teradata IDE. New Export and Import menu items are provided as part of the Teradata SQL History View toolbar.
LOB support includes the ability to view LOBs within the Result Set Viewer, and include LOBs as parameters when running parameterized SQL. When a query result is being processed and a result column contains an LOB, a dialog appears. The dialog requests information about where the LOB values are to be stored on the file system, what the base name of the files is to be (initially the column’s name), what the file extension should be, whether the contents of image values are to be shown as images in the result set view, and whether image values are to be saved when the images are displayed in the result set view. When LOBs are needed for parameters to a SQL statement, the Configure Parameters dialog allows the user to specify the location of the LOB file.
This feature provides an enhancement to the current SQL Ant Wizard that allows the user to use parameter substitution for the selected SQL queries. The user can enter values for each of the SQL parameters. These parameter values are stored in a properties file to be provided with the SQL Ant script. Parameter properties make the script more reusable. The Ant script can be configured by updating the properties file instead of changing the script directory. It facilitates the SQL Ant script usage for creating CVS files, installation, and testing.
The Schema Cache option allows the user to designate particular schemas (databases/users) to be cached. A schema cache file that contains the metadata for the schema is created. The metadata describes all the information about the schema, such as its tables, columns, constraints, indexes, macros, parameters, stored procedures, user defined functions, user defined types, views, and so forth. The schema cache is associated with the connection profile. If the connection profile is deleted, so is the schema cache list and any schema cache files that were created. The schema cache files are stored in the workspace /.metadata directory.
When the user first connects to the database and opens the Schemas folder, the schema cache file is created in a background job. Once the cache is created, if the user refreshes the list of schemas (by clicking the Refresh menu option on the Schemas folder), the cached schemas are loaded from the schema cache file. The schema is then highlighted within the Data Source Explorer with the cache icon, . It should be noted that any modifications that are made to objects of a cached schema are not reflected in the cache. The user must refresh the schema cache for those changes to take effect.
This feature provides an option for users to manually enter a JDBC property and its value. This is useful when non-standard JDBC properties are required for the Teradata connection. In the drop down list of JDBC Properties, scroll down to the bottom and select the USER_ENTERED_PROPERTY option. A dialog appears for you to enter your JDBC property name and its value. The name/value pair is then stored and passed to the JDBC driver when creating a connection to the Teradata Database.
If you are new to the Eclipse world, there is an article to help you get up and running. Please refer to Getting Started with Teradata Plug-in for Eclipse.
Online Help can be accessed within the plug-in in two ways:
Reference Documentation can be found on the download page or at: www.info.teradata.com