-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No support for writting TIMESTAMP #8
Comments
Could you please try to use the latest version of the driver? |
Thank you for your attention. |
Yes, this is the correct location. To be sure, we uploaded the latest right now again. Please try one more time. |
I keep getting the same error. The latest version of the driver is 1.14.0, according to the repository 'com.github.albfernandez:javadbf' and it's the same version included in your driver. Is there an alternative to save only some specific tables where there are not timestamp fields. The tables I'm updating doesn't contain this type. |
I added a fix. A new library is deployed. Timestamps will be saved as text.
case "timestamp":
if ( DBFDataType.TIMESTAMP.isWriteSupported() ) {
field.setType( DBFDataType.TIMESTAMP );
} else {
field.setType( DBFDataType.CHARACTER);
field.setLength( 256 );
}
|
Hi,
I get this error when I try to save the database:
java.lang.IllegalArgumentException: No support for writting TIMESTAMP
at com.linuxense.javadbf.DBFField.setType(DBFField.java:431)
at com.wisecoders.dbschema.dbf.schema.Table.createDBFField(Table.java:48)
at com.wisecoders.dbschema.dbf.io.H2Writer.(H2Writer.java:38)
at com.wisecoders.dbschema.dbf.H2Connection.saveDbf(H2Connection.java:154)
at com.wisecoders.dbschema.dbf.H2Connection.access$100(H2Connection.java:38)
at com.wisecoders.dbschema.dbf.H2Connection$StatementProxy.invoke(H2Connection.java:90)
at jdk.proxy3/jdk.proxy3.$Proxy137.execute(Unknown Source)
I thought that it was a problem with the insert clauses I made, but it occurs although saving without updating the database.
The text was updated successfully, but these errors were encountered: