-
As far as the mapping of the NUMBER(10,0) to Long is concerned, I think the current code would do it, as long as your driver is returning a NUMERIC or DECIMAL as type for the column.
Please try to get rid of the classes12.jar in the sql2java classpath and drop there your own driver for your version (not described in your post). The classes12.jar was the driver for Oracle 9i.
Regards...
2009-02-17 16:05:55 UTC in SQL to Java Code Generator
-
The mappings between SQL types and Java types are defined in the code of class Column where in internal (sql2java specific) mapping type is used.
sql2java/src/java/net/sourceforge/sql2java/Column.java
My guess is that the whole mapping depends on the Java type returned by your driver. Did you try with the driver provided with your Oracle version? It seems to me that the classes12.jar...
2009-02-17 15:54:27 UTC in SQL to Java Code Generator
-
The DAO classes and interfaces are generated based on the procedures found in the database. This was an experimental set of functionnalities but the association of procedures to tables was not quite clear.
Just erase the spdao (Stored Procedures Data Access Objects) template from your list of generated folders.
Regards,
Alain.
2009-02-17 15:45:00 UTC in SQL to Java Code Generator
-
The DAOException is defined in the template
sql2java/src/templates/velocity/java/perschema/exception/dao.exception.java.vm
where you can make the change.
Regards,
Alain.
2009-02-17 15:39:00 UTC in SQL to Java Code Generator
-
kameleono committed patchset 280 of module sql2java to the SQL to Java Code Generator CVS repository, changing 2 files.
2008-11-17 13:10:59 UTC in SQL to Java Code Generator
-
The same fillPreparedStatement() method is used for both selection and update situations.
While the currently implemented code is fully functional for updates and creations, it should omit the setNull() call when used after the fillWhere() method was called, meaning there will be a selection or deletion.
2008-11-10 18:14:53 UTC in SQL to Java Code Generator
-
The original design pattern intended to avoid the direct instantiation of the MyBean class. The only legal way to obtain a new instance was through the createMyBean() method of the MyManager. As you moved around the classes, the design choice cannot be applied anymore.
The only solution I can think of was already given by the previous comment.
Regards,
Alain.
2008-11-10 14:10:41 UTC in SQL to Java Code Generator
-
kameleono committed patchset 279 of module sql2java to the SQL to Java Code Generator CVS repository, changing 3 files.
2008-11-05 16:47:05 UTC in SQL to Java Code Generator
-
kameleono committed patchset 278 of module sql2java to the SQL to Java Code Generator CVS repository, changing 13 files.
2008-06-02 11:43:13 UTC in SQL to Java Code Generator
-
kameleono committed patchset 277 of module sql2java to the SQL to Java Code Generator CVS repository, changing 3 files.
2008-06-02 11:33:25 UTC in SQL to Java Code Generator
