The basic RM functions (find, insert, update and delete) now have cached and uncached variants. The old methods (such as find and findK) are now cached, and new methods (such as findUncached and findKUncached) are uncached.

The cache size can be configured in the RacoonConfiguration object.

A new method has been added: refresh. It allows to refresh the cache of a given object by executing the findUncached method.

The LazyId does not have an empty method anymore, and the get method cannot return a null value. If a property of a Table can be null, make the LazyId itself nullable.

A small fix of the update method is also included.

Is your feature request related to a problem? Please describe. Always have to check if the value of a LazyId is null or not makes the code "heavy". Also there are cases where a LazyId cannot have a null value (for example when a foreign key has a NON NULL)

Describe the solution you'd like Splitting the LazyId class into different classes:

• a generic one (the current LazyId)
• a null one
• a non-null one

Note that LazyId would then become a sealed class and the variants would be subclasses.

Describe alternatives you've considered Probably also splitting the non-null variant into:

• a non-null lazy one
• a non-null defined one

could be useful

Additional context No.

The ParameterCaster interface can now be used to achieve more complex behaviours. A prefix and a postfix can be optionally be defined such that when executing auto-generated queries (for example when using the insert or find methods), the resulting query is customized with these two new properties

If a connection is idle for more than the specified time in the idleTimeout settings, the connection will be closed and when a new one is requested, a new one is created instead of the same one being used.

The old behavior of the idleTimeout is replaced by the new property socketTimeout.

If a connection is idle for more that the specified time in the idleTimeout settings, the connection will be closed and when a new one is requested, a new one is created instead of the same one being used.

The old beaviour of the idleTimeout is replaced by the new property socketTimeout.

Describe the bug A class using the Table interface doesn't work as expected if one of the properties is an unsigned one. This happens only when a value is set using parameter binding.

In particular, this exception is thrown when executing a query with an UInt being used as a parameter:

java.sql.SQLException: Cannot convert class kotlin.UInt to SQL type requested due to com.mysql.cj.exceptions.WrongArgumentException - Invalid argument value: java.io.NotSerializableException

To Reproduce Steps to reproduce the behavior:

1. Create a class that implements the Table interface
2. Create a property with an unsigned Kotlin type
3. Execute a query that sets the previously defined property as a parameter of the prepared statement
4. See the exception above

Expected behavior Unsigned types should be supported??

Screenshots No.

Version

• MySQL: Any
• Racoon: 0.1.2b and earlier (and probably newer)

Additional context This can't probably be fixed. Unsigned types are not supported by Java, and so not supported by the MySQL connector. A possible fix would be to cast an unsigned type to its corresponding signed one, but it would be more confusing than declaring the field signed in the first place. Another possible fix would be to cast the unsigned type to String and let MySQL handle the conversion after, but this seems a cheap trick that could prevent Racoon from working with other DBMS in the future.

Describe the bug LazyId should not be used with a delegation. Using it this way makes the code more error-prone and inefficient. For example, suppose only the id needs to be retrieved from the object when using the delegation pattern. In that case, a whole new query and mapping must be done, while when using the LazyId, the id can be collected directly.

Expected behavior No.

Screenshots No.

Version

• MySQL: Any
• Racoon: Latest branch

Additional context No.

Describe the bug The idleTimeout property of the ConnectionSettings does not change the actual idle time of the connection.

To Reproduce Steps to reproduce the behavior:

1. Use a ConnectionSetting instance with a short idleTimeout;
2. Request a connection from RacoonDen and release it;
3. Wait for the defined `idleTimeout.

Expected behavior The ping test while requesting the next connection, should be negative, but its positive (it depends on the configuration of the Database itself)

Screenshots No.

Version

• MySQL: Any
• Racoon: Latest branch

Additional context A series of queries should be used instead of the idleTimeout URL parameter: https://dba.stackexchange.com/a/174640

Is your feature request related to a problem? Please describe. No.

Describe the solution you'd like An enum should be used as the type of a property in the primary constructor. The enum should implement an interface which defines the correlation between the in-code enum constant and the in-database enum constant.

Describe alternatives you've considered Maybe leave the opportunity to use enums without a specific interface implementation, such that less runtime-errors occurs.

Additional context No.