keyholder | Store Data About Rows | Database library

In your json posted above the name of the id property is articleid whereas in the pojo it's id, so the value has just not been mapped to the pojo's id property. Make them same names

In the default situation, Spring's JdbcTemplate will use JDBC's Statement.RETURN_GENERATED_KEYS option. The problem is that the Oracle JDBC driver will not return the value of an id column for that option, but instead return a 'row id' (basically an internal pointer to the row, not the id value in that row). This is not suitable for most use cases, as it would require you to explicitly query the row using the row id to obtain the actual id value, and specifically in the implementation of Spring's KeyHolder it results in the mentioned error, because a java.sql.RowId implementation is not a long (nor a subclass of java.lang.Number).

Fortunately, JDBC offers additional methods to obtain generated columns: by explicitly specifying the column names (or column indexes) of the column(s) you want to have. That is what new String[] {"ID"} does. It instructs JdbcTemplate to pass this array of column names to the JDBC driver, and the driver - assuming it supports this feature - will return the specified column(s), that is if your table actually has a column with the name ID.

In other words, this does not "cast ID to a string array and then fetch its long value", it will retrieve the value of the column ID instead of the Oracle JDBC driver returning the 'row id' of the inserted row.

The question you link to is specifically about Oracle (which defaults to returning a row id). The reason the Oracle JDBC driver returns a row id is because until recently Oracle did not have identity columns, and the only way to have identity-like behaviour was to use custom triggers to generate IDs. This makes it impossible to determine if a table has generated columns, and if so which column(s). Instead the implementation decision was to return the row id unless explicit columns were specified.

Although this problem is specific to Oracle, other drivers may have different problems that may need to be solved using the same solution: for example some drivers (e.g. PostgreSQL and Firebird (Jaybird, the Firebird JDBC driver I maintain)) will default to returning all columns, and if your ID column is not the first column, this may result in similar errors because the Spring GeneratedKeyHolder.getKey() method assumes the generated id is held in the first column of the generated keys result set.

The question can be considered as closed as the related feature request is registered in the issue tracker.

@speendo - Kindly use setNull method of PreparedStatement with using java.sql.Types as below:

There's a JDBC driver bug SR 3-18090632291. Some info an be found here:

• https://github.com/jOOQ/jOOQ/issues/7962
• https://twitter.com/AFulgens/status/1227148982259982337

This is really difficult to work around, because the JDBC driver tampers with the SQL string, and you cannot really do anything about that.

Well, your code is a lot to take in but it looks like the for loops at the bottom are being called outside of the subscribes. Since this is asynchronous code, the values in the for loops are undefined or empty when the functions run because the values you are getting from your firebase calls are not yet returned. When you call subscribe, the code execution moves on while a second thread waits for the response to execute the code inside the subscribe.

You need to change

I found the answer to this problem.

Bouncycastle does not add a0:00 to the attributes when no attribute instance is given (null). This leads to incomplete encoded data.

"If you just see: Attributes: then the SET OF is missing and the encoding is technically invalid (but it is tolerated)." - https://www.openssl.org/docs/man1.0.2/man1/openssl-req.html

The solution is to provide a empty DerSet to the CSR which leads to the a0:00 generation indicating there are no attributes present.

Try adding