
SQL Assistant Java Edition
SQL Assistant Java Edition is an information discovery tool that retrieves data from Teradata Database systems and allows the data to be manipulated and stored on the desktop. It is built on top of the Eclipse Rich Client Platform (RCP). This allows the product to take advantage of the RCP framework for building and deploying native GUI applications to a variety of desktop operating systems. SQL Assistant Java Edition can be run on Windows, Linux, and Mac OSX operating systemts. The Eclipse platform is designed as an open tools platform but architected so that its components (or a subset of its components) can be used to build RCP applications. This allows SQL Assistant Java Edition to benefit from the many high quality Eclipse features available while focusing on value-add for Teradata.
SQL Assistant Java Edition includes the following key features:
- Modular display that allows you to move panels around, creating a custom look and feel.
- Data Source Explorer to view database objects, such as schemas , tables, macros, stored procedures, user-defined functions, user-defined types, views, and triggers. (NOTE: SQL Assistant Java Edition uses the term schema to refer to a database.)
- Data Source Explorer menu options to run Stored Procedures, Macros, and User-defined Functions.
- Connection Profile Wizard to create connection profiles using the Teradata JDBC Driver.
- SQL Editor to create, modify, and execute individual or multiple SQL Statements, including parsing the SQL statement for syntax errors and formatting the SQL according to selected formatting options.
- Result Set Viewer that creates a historical record of the submitted SQL queries with time stamps, status information, and result set data.
- Ability to export result set data as plain text, XML, HTML, CSV, as well as Excel format.
- SQL Query Builder to visually build and edit SQL queries.
- Data wizard to extract data from the Teradata Database to a file on the desktop.
- Data wizard to load data from the desktop file system to the Teradata Database.
Modular Display
The SQL Assistant Java Edition display includes the SQL Assistant Toolbar along with five view panels: the Data Source Explorer View, the Project Explorer View, the SQL Editor (SQL Scratchpad), the SQL Results View, and the Teradata View.

SQL Assistant Java Edition contains a toolbar that provides buttons to allow quick access to functions that are used while creating and modifying SQL files.
A view can also contain its own toolbar and drop down menu. These toolbar buttons and menu items provide actions on the data managed by the view. Included in the view toolbar are buttons to minimize, maximize, and restore the view. Maximizing the view will cause the view to take over the entire SQL Assistant Java Edition window display. Click the Restore button to return the view back to its previous display.
You can customize the look and feel of SQL Assistant Java Edition by moving view panels within the main display window. A view can be moved by selecting the view and dragging it to a new location. As you move the view over the display, the mouse pointer will change depending on where you want to drop or dock the view. You can also drag the view outside the display area. The view will then become a "detached" view. You can also remove a view panel by clicking the "X" on the view tab. A view can be re-displayed by selecting the view from the Windows>Show View option in the main menu.
Data Source Explorer View
The Data Source Explorer View panel contains the database object tree display. It is here that you can create connection profiles to your Teradata Database systems and interact with the database objects.

Creating Connections
You can create connections to your database using the Connection Profile Wizard. The wizard is invoked from the Data Source Explorer by right clicking on the Database Connections folder.


The Connection Profile Wizard is based on a driver template that references an embedded Teradata JDBC driver. Enter the database server name, user name, password, and default database name into the wizard dialog screen. Optionally, you can choose a different Teradata JDBC driver than the embedded Teradata JDBC driver, as well as add properties for the database connection.
Creating a SQL Statement (SQL Scratchpad)
When SQL Assistant Java Edition is launched, a SQL Scratchpad area is provided for you to enter your SQL statements. Once you have a connection to your Teradata database, you can begin to enter SQL statements in the SQL Scratchpad window. Click the Save button to save the SQL Scratchpad to a file.

Another option to create a SQL file is through the Data Source Explorer. Within the Data Source Explorer, select your database connection and click the SQL Scrapbook action from the Data Source Exporer toolbar. This will create a SQL file in the SQL Editor with the name 'SQL Scrapbook [n]' and the connection profile set to your database connection. You are now ready to enter your SQL statement. Refer to the section below entitled 'SQL Editor' for information on executing your SQL statement. Click the Save icon to save your SQL file within your SQL Project.
.jpg)
Edit, Extract, and Load Data
The Data Source Explorer also provides an option to edit, extract, and load data into a given table. Right click on the table and select the option from the drop down context menu.

The Edit option will present the current rows of data from the table in a table grid display within the SQL Editor. You can click on a cell in the table grid to modify the cell contents or add a new row by clicking on the <new row> entry. Depending on the edit option, a SQL UPDATE, INSERT, or DELETE statement is created and run. The results are displayed in the SQL Results View.

The Load option will present a dialog to choose the file to load and define the necessary file format needed to identify columns when loading data into the table. File format options include the column delimiter (comma, semicolon, space, tab, or vertical bar “|”) along with the character string delimiter (double quote, single quote, or none). It will create an INSERT statement for each row of data in the file.

The Extract data option will present a similar dialog for you to enter information about the file created from the extracted data, such as the output file and output file format (column delimiter and character string delimiter options).
The Sample Contents option will perform a “SELECT * FROM” SQL operation on the table and display the results in the SQL Results view.
Project Explorer View
The Project Explorer View panel provides a hierarchical view of the Projects and their resource files. It is here that you can select SQL files for editing or create new SQL files. SQL files can also be imported from or linked to your file system. When Teradata SQL Assistant is first installed, an initial project called 'SQL' is created for you. You can create additional projects using the New>Project... menu option.

Within the Project Explorer, you can also choose an option to compare two files. The Compare Option displays the two files side by side with buttons that allow you to jump from one difference to another or move changes from one file to another. This is very handy when comparing SQL files or result set data.
SQL Editor
The SQL Editor view is displayed when a SQL file is opened. Double clicking on a file in the Project Explorer will cause the file to be opened in the SQL Editor.

The SQL Editor provides a scratch pad for you to enter your SQL statements. As you type, SQL content assist will pop up annotations showing a list of expected keywords. If a database (or schema) name is entered followed by a dot, the content assist will display the list of tables from your schema for you to select from. (Note: You must be connected to a Teradata Database in order for SQL content assist to work.) The SQL Editor also provides syntax coloring for your SQL statements. You can change the colors of comments, keywords, identifiers, types, or other syntax items via the SQL Editor Preferences page.
When right clicking in the SQL Editor window, a SQL Editor Context menu appears with options to execute the SQL statement(s) in your SQL file.

The following options are presented:
- Execute all of the SQL statements
- Execute the selected SQL statement
- Execute the SQL statements as individual statements (with a commit occurring between statements)
- Execute the selected statement as one statement
- Execute the current statement where the cursor is located
- Visual Query Builder
SQL Assistant Java Edition provides a graphical interface for creating SQL statements, referred to as the SQL Query Builder. You can edit an existing statement using the SQL Query Builder by selecting the statement within the SQL Editor and choosing the ‘Edit in SQL Query Builder…’ menu option. (Refer to figure above).

You can add additional tables and table joins by right clicking in the SQL diagram area and select Add Table… or Create Join…. When adding a table, a list of tables and views is presented for you to choose from. Additionally, from the SQL text window, you can choose an option to run the SQL statement. A SQL Results tab is provided for you to see the result set data.
SQL Results View
The SQL Results View displays the result data from executing SQL statements and running database routines, such as stored procedures, macros, user-defined functions, and triggers.

You can select a result entry from the history list and re-execute it or re-open it in the SQL Editor. This allows users to further fine tune their SQL statements.
The SQL Results View also provides an option to query the result history for particular SQL operations. You can enter your query in the space 'Type query expression here'. This will use the Apache Lucene query engine to search the SQL results history.
.jpg)
Exporting Result Data
SQL Results can also be saved to a file within your Project or exported to an external file in the file system. This can be invoked by right clicking in the result data area and choosing the Save or Export option.

If the Export option is chosen, the Export Result dialog is displayed. Select a file name, format, and export options. Then click the finish button to create the exported file. The Save option presents a similar dialog.
The following screen capture shows the result data with totals on integer columns as exported to an Excel file.
Teradata View
The Teradata View contains more detailed information about the database objects. When an object is selected in the Data Source Explorer, it is automatically displayed in the Teradata View. You can click on the tabs to display additional information on the database object.

.jpg)
Help
Help is provided by clicking on the Help>Help Contents in the main toolbar.
.jpg)
Conclusion
While SQL Assistant Java Edition is not necessarily intended to replace the current Teradata SQL Assistant product it does allows us to offer an alternative for customers whose client platform includes systems other than Windows. Supporting multiple platforms (Windows 32/64, Linux 32/64 and Mac OS X) in this way allows customers to be flexible when choosing a client operating system to connect to their Teradata Database system.
To get up and running with Teradata SQL Assistant Java Edition use the Download links above or go to the Tools Download area, pick your OS and take a look at the README.
I recently downloaded and started using the SQL Assistant Java Edition. Although it is functional and conveniently light weight, I struggled a bit with the User Interface and, as the name implies, I expected it to look a lot more like the original SQL Assistant (Queryman). The original has a UI that has been perfected over many years and has to be the most used and most loved Teradata application. I'd like to open this up for discussion, it is my feeling the the Java Edition should have very similar look and feel to the original if it is going to be widely accepted. It should need no instructions and no documentation. As with the original, you should not even have to be familiar with SQL to start writing complex queries and stored procedures (query builder).
Not sure that SQL Assistant is the most loved Teradata application
;)
First off a Disclaimer: I am responsible for the Tools content on Teradata Developer Exchange so all of the articles in the Tools section are close to my heart. I'm also a Java developer and have been working with Eclipse based tools since before it was even called Eclipse (anyone remember WSAD) so I'm pretty comfortable with the UI.
That said, SQL Assistant Java Edition was created as an off shoot of the Teradata Plug-in for Eclipse activity, which is focused on helping developers to create applications (obviously including SQL) for use on Teradata. This use of Eclipse dictates some of the UI aspects of the product and I would contend that there is sufficient weight behind Eclipse.org that their UI decisions are good enough.
With SQL Assistant Java Edition (marketing chosen name) we were asked to provide a "Single Click Install" version of the SQL oriented part of the Teradata Plug-in for Eclipse in order to support a wider range of Operating Systems and Users than the existing SQL Assistant (windows) product. We are not trying to replace SQL Assistant, rather we wish to introduce a whole new set of users to Teradata.
The developers of the Teradata Plug-in for Eclipse and SQL Assistant Java Edition are prolific contributors to the Tool section of Teradata Developer Exchange (for which I commend them) and I would point the audience to their many articles as a quick way to get up and running with Teradata Plug-in for Eclipse, SQL Assistant Java Edition and Teradata.
MikeC....
I think it deserves a new name, just because.
I think hyperj's comment is really just pointing out that the default view of SQLA-JE doesn't actually have an area to enter SQL. I think it should be there as part of the default view, since after all, when starting this tool you probably want to enter SQL ;)
I agree with hyperj, SQLA is the TD application I have used the most so far.
Autocomplete of column names doesn't work in SQL editor while using table aliases. It works only in Query builder.
Yes. The reason being is that the SQL Editor is using strictly a token based parser. It has a very narrow focus. The Query Builder is collecting more information at a wider scope, for example keeping track of the aliases, to help the user build SQL.
Hello fgrimmer, why can see more than 500 line in de result of the query?.
If I change this parameter for 2000 line an error occurs......
Hello fgrimmer,
I downloaded the SQL Assistant Java Edition and i think that it is incredible !!!!!!!.
I have a question ... How can I add Tasks ?
The result set preference error is occurring in the Eclipse DTP code. We are looking at a possible work around.
As for adding tasks, can you be more specific? SQLA JE has a concept of Run Configuration tasks, where you can configure runnable SQL statements. Is that what you are referring to?
hello fgrimmer, thank for your answer,
Is any difference conect it for JDBC or ODBC? which is more efficient?
I am not the best person to answer that. There are many factors and opinions that could argue either way. This question is better handled on the DevX Connectivity forum.
Hi fgrimmer, I have a question....How can I look the explain of the query (shortcut)?
You can perform a SQL "explain" on a query, such as:
explain select * from dbc.dbcinfo;
and the result is displayed in the SQL Results View for that query.
It is correct but the question was whether there was any key combination such as F6 in Sql Assistant.
No, not at this time.
湘西 2007 »¤Ô«ÏØ
湘西 2001 ¼ªÊŒÊð
It's problem ,The result in Chinese.
Can you give more information on how the problem occurred?
Hi there,
The Eclipse port really goes the right direction ... congratulations!
Questions:
1) How do i specify the mechanism? We use ldap. Is there a substitute for the usergssconfig-file?
2) can the client be installed really standalone without any other packages?
Thanks in advance!
BR
Anton
Hi, a question about the migration scenario from the old assistant:
How can we convert the locally stored SQL statement history? Where/how is the new history stored?
The old one uses afaik a access mdb database ... the new edition a flat-file history? There should be a way to convert the history, because our users need it badly.
Thanks!
1) The ability to specify LDAP and Kerberos is coming soon.
2) The SQLA Java Edition contains the necessary pieces to connect to Teradata. It requires the Java VM.
The migration of the original SQLA's history is on the list of features under consideration.
SQLA Java Edition's history is stored as serialized Java objects in the workspace's metadata repository (in the directory .metadata\.plugins\ org.eclipse.datatools.sqltools.result under the workspace). Since they are serialized objects, there isn't the opportunity to create a migration tool by editing them.
Our customer is interested in an official version of Java SQL Assistant. Does exist any time plan for the SQL Assistant release?
Otakar
SQL Assistant JE should be officially released this month (December).
How much does it cost to buy the official SQL Assistant
SQL Assistant JE will be available from the Developer Exchange downloads at no cost.
Hi,
Normally Eclipse creates the workspace in the user's home directory.
In the SQLA RCP, it is created under the installation directory (which is not possible in our installations due the lack of user rights).
This makes it also unusable in out Terminal Server scenario ... :-(
How can I force the workspace creation in the user-home folder?
Thanks!
The workspace is created in the working directory on Windows and Linux and the user's Documents directory on Mac.
The just-released version of SQLA-JE's installation process creates desktop and Start menu shortcuts that set the working directory to the user's home directory so that's where the workspace will be created.
If you're using the Windows alpha version, you can create a shortcut with the "Start in" directory set to the location you want the workspace.
It would be nice to see named parameters support in one of the future versions. I'm really missing this handy feature of regular SQL Assistant. Otherwise - great application.
Named parameter support is coming.
After Installation: Teradata SQL Assistant Java Edition for MAC OS X, I am unable to run the Application, its giving following error: "You can't open the application "Teradata SQL Assistant" because its not supported on this architecture". I am having Mac OS X version 10.5.8, Plz let me know the what needs to be done.
Can you verify that you have the correct Java Runtime, version 1.5 or greater.
FORMAT doesn't work - output is unformatted. FORMAT works in the original version ("Queryman").
e.g. SELECT TheTime(FLOAT,FORMAT'99:99:99') FROM SW_Event_Log
I tried to change connection parameter TMODE (ANSI,TERA,DEFAULT) - nothing helps.
The FORMAT command is performed by the Teradata Database when in field mode. This option is not supported by the JDBC Driver, at this time. As well, the format information isn't readily available to SQLA JE to get and process for displaying the result data. It is recommended that you use Excel to format your result set data.
Hi!
is there any progress on getting LDAP working?
Will there be an update-site for getting the installation and the updates for the plugin's?
Thanks!
Is it possible to create a connection without saving a password ?
Is the saved password hackerproof (where is it saved, which type of encryption is used, ...) ?
LDAP and Kerberos support has been implemented and will be available in the next release. For SQLA-JE we will make pre-release versions available with incremental functionality. The planned official release with this content is 2Q 2010.
Currently it is not possible to create a connection profile without saving the password. It is stored in a .plugin directory for connectivity. This file is managed by the underlying Eclipse technology and is encrypted with DESede (triple DES).
Is not saving the password and soliciting it an option that is desirable or required?
Soliciting (not saving) password is a required option (security policy).
The FORMAT keyword is not supported by the Teradata JDBC Driver. Original SQLA uses the Terdata ODBC Driver and supports FORMAT keyword. I think that SQLA-JE is a little bit of a "downgrade" in this case.
Will support of the FORMAT keyword be implemented in the future? Thanks.
We'll make saving the password optional so that if it is not saved it will be solicited.
There are not plans to provide the functionality of the FORMAT keyword at this time. Again, we are referring this functionality and other formatting options to a tool, such as Excel.
How do you format the appearance of the SQL results. The font used, the size etc. The default does not seem to be very readable.
The best option for formatting your result set data is to run your query and save or import the result set as Excel. Then use Excel to change the font, size, etc.
I downloaded the SQLJE and installed it, when I click on it to run (in windows) it brings up the splash screen, then just goes away. Nothing starts up, the process just goes away with no errors and no indication that anything was wrong.
Tuen, which version of Windows are you running on? And which version of Java is installed?
When SQLA-JE runs, it creates a folder called "workspace" in the folder specified in the "Start in" field of the shortcut used to start the application. This is set to be your home directory (usually C:\Documents and Settings\your-user-name). In that folder it creates a folder called ".metadata". Inside that folder a file called ".log" receives log messages from the application.
Has a HOME_FOLDER\workspace\.metadata\.log file been created? If so, is there anything in it that indicates a problem?
We haven't seen the problem you have described. We'll need more information to try to figure this one out.
Hi I downloaded the 64bit Version for Linux (OpenSuse 11.2 64bit) and the 32bit for Windows (Win XP). I have the same issue on both versions. When I try to extract a table SQL Assistant is refusing to export decimal data types.
When I try to unload the result set I am not able to get more then 500 rows. When I try to change the default value in the preference section I will get an error:
Error notifying a preference change listener. Check the log for details.
java.lang.String cannot be cast to java.lang.Integer
Furthermore:
org.eclipse.swt.SWTException: Widget is disposed
Problems occurred when invoking code from plug-in: "org.eclipse.jface".#
Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
I am using for the SQL Assistant the Java version 1.6.0 but I also have installed 1.5.0 (used for other apps.)
This happens in any case (0 for unlimited or any number I type in). The value is stored in the preferences but the resultset remains unchanged at 500 rows.
What can I do to either display all data types or increase the number of rows in the result set? The described behaving appears on both Versions and both OS in exactly the same way.
The problem you mentioned regarding setting the result set size has been fixed in the Eclipse DTP code. We are in the process of testing and should have a SQLA JE release out soon that resolves that problem.
For the other problem regarding exporting decimal data types, I would need more information. Are you choosing the Export option in the SQL Results View? What is it showing for the decimal value? Is there an error message displayed in the Error Log? To display the Error Log, go to Window>Show View>Other.. and select General>Error Log.
Thanks for replying. The result set of a query displays the Decimal Datatypes correctly. But when I try to export the result I have the mentioned limit of 500 rows.
The Problem with the Decimals appears when I am trying to extract a complete table from the Table or View list. SQL Assistant ist extracting the content but when finished it tells me the follwoing (in the SQL resultset next to the list of queries:
Extracting [Table] ...
Data extraction was successful.
13561 row(s) extracted.
One or more values could not be retrieved in the following column(s): Col1, Col3
Col1 and Col3 are Decimal Datatypes. The List of the SQL statements I have a warning sign in front of the SQL.
When I am using a different table the same happen again, just the Decimal will be rejected.
The Error Log says the following:
Widget is disposed
org.eclipse.swt.SWTException: Widget is disposed
at org.eclipse.swt.SWT.error(SWT.java:3884)
at org.eclipse.swt.SWT.error(SWT.java:3799)
at org.eclipse.swt.SWT.error(SWT.java:3770)
at org.eclipse.swt.widgets.Widget.error(Widget.java:450)
at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java :388)
at org.eclipse.swt.widgets.Text.getText(Text.java:963)
at org.eclipse.ui.dialogs.FilteredTree$3.getName(Filtered Tree.java:630)
at org.eclipse.swt.accessibility.AccessibleObject.atkObje ct_get_name(AccessibleObject.java:395)
at org.eclipse.swt.internal.gtk.OS._gtk_widget_destroy(Na tive Method)
at org.eclipse.swt.internal.gtk.OS.gtk_widget_destroy(OS. java:11922)
at org.eclipse.swt.widgets.Widget.destroyWidget(Widget.ja va:412)
at org.eclipse.swt.widgets.Widget.release(Widget.java: 1054)
at org.eclipse.swt.widgets.Control.release(Control.java: 3293)
at org.eclipse.swt.widgets.Widget.dispose(Widget.java: 446)
at org.eclipse.ui.internal.PartPane.dispose(PartPane.java :180)
at org.eclipse.ui.internal.ViewPane.dispose(ViewPane.java :193)
at org.eclipse.ui.internal.WorkbenchPartReference.dispose (WorkbenchPartReference.java:681)
at org.eclipse.ui.internal.WorkbenchPage.disposePart(Work benchPage.java:1715)
at org.eclipse.ui.internal.WorkbenchPage.partRemoved(Work benchPage.java:1707)
at org.eclipse.ui.internal.ViewFactory.releaseView(ViewFa ctory.java:256)
at org.eclipse.ui.internal.Perspective.hideView(Perspecti ve.java:606)
at org.eclipse.ui.internal.WorkbenchPage.hideView(Workben chPage.java:2381)
at org.eclipse.ui.internal.ViewPane.doHide(ViewPane.java: 213)
at org.eclipse.ui.internal.PartStack.close(PartStack.java :543)
at org.eclipse.ui.internal.PartStack.close(PartStack.java :526)
at org.eclipse.ui.internal.PartStack$1.close(PartStack.ja va:122)
at org.eclipse.ui.internal.presentations.util.TabbedStack Presentation$1.handleEvent(TabbedStackPresentation.jav a:83)
at org.eclipse.ui.internal.presentations.util.AbstractTab Folder.fireEvent(AbstractTabFolder.java:270)
at org.eclipse.ui.internal.presentations.util.AbstractTab Folder.fireEvent(AbstractTabFolder.java:279)
at org.eclipse.ui.internal.presentations.defaultpresentat ion.DefaultTabFolder.access$1(DefaultTabFolder.java:1)
at org.eclipse.ui.internal.presentations.defaultpresentat ion.DefaultTabFolder$1.closeButtonPressed(DefaultTabFo lder.java:70)
at org.eclipse.ui.internal.presentations.PaneFolder.notif yCloseListeners(PaneFolder.java:626)
at org.eclipse.ui.internal.presentations.PaneFolder$3.clo se(PaneFolder.java:206)
at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.j ava:2199)
at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFo lder.java:327)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTabl e.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java: 1176)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Disp lay.java:3493)
at org.eclipse.swt.widgets.Display.readAndDispatch(Displa y.java:3112)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workben ch.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java :2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.j ava:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java :500)
at org.eclipse.core.databinding.observable.Realm.runWithD efault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbenc h(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(Platfo rmUI.java:149)
at com.teradata.sqla.Application.start(Unknown Source)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run( EclipseAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLa uncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLa uncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Ec lipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Ec lipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMeth odAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Delega tingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main .java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java: 514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
But I think this is not related to the error, since I will get this message as soon as I am opening the Error log.
There is not much else in the Errorlog (I deleted it), at least nothing which obviously is related to the warning.
When I am opening the exported file I can find all exported values except the Dezimal. They appear to be NULL (I used the | (pipe) sign as a field sperator) at least th row look like this:
|abcdedv||343|2009-02-10|...
Col1 and Col3 supposed to hold the decimal values.
Thanks
Thank you for the trace. This, too, is an Eclipse DTP problem that we are tracking. We hope to have a SQLA JE version with a fix soon.