• 1 reply
  • Latest Post - ‏2012-04-11T13:31:45Z by DGawron
1 Post

Pinned topic Using WEF CRUD for IBM-Netezza Appliance tables?

‏2012-04-09T17:11:00Z |
Has anyone hooked up a WEF front-end to an IBM-Netezza appliance? Does anyone have suggestions on how to approach this?
I would like to use WEF to build on-line maintenance pages for look-up and reference tables on our IBM-Netezza data warehouse appliance. The tests that I've built so far with simple SQL Data Services or SQL Call builders are failing on actions that try to modify the Netezza table (insert / update / delete).

The exception thrown is "org.netezza.error.NzMethodNotImplementedException: netezza.unimplemented".

I contacted Netezza support and they indicated that not all parts of the JDBC spec have been implemented in their JDBC JAR.

Other misc info:
  • I do have rights to update the table.
  • I was able to write a command-line Java program that uses the Netezza JDBC Jar library to prepareStatement(qry) and stmt.executeUpdate() on the table.
  • Netezza support responded with:
And here is the list of methods that we do not support:
1. prepareStatement(String sql, int autoGeneratedKeys)
2. prepareStatement(String sql, int[] columnIndexes)
3. prepareStatement(String sql, String[] columnNames)
  • Stack Trace generated by the WEF code:
org.netezza.error.NzMethodNotImplementedException: netezza.unimplemented
at org.netezza.sql.NzConnection.prepareStatement(
at org.tranql.connector.jdbc.ConnectionHandle.prepareStatement(
at genjava._mdlNzEmp.dataSvcNzEmpCrudUpdateInvokeBase(
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
Updated on 2012-04-11T13:31:45Z at 2012-04-11T13:31:45Z by DGawron
  • DGawron
    251 Posts

    Re: Using WEF CRUD for IBM-Netezza Appliance tables?

    It's very unlikely you'll be able to use the SQL builders with Netezza because of the incomplete Netezza JDBC driver implementation. What I would suggest is to create one or more LJOs that call Netezza directly and avoid the unimplemented parts of JSBC.