You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, does spring-data-jdbc support logical pseudo-delete fields? When querying or saving, add a pseudo-delete query condition or provide a default value when saving (although it can be set through the default value of the database). Checking the source code is visible in the SqlGenerator package, and no corresponding configuration items are found. Is there a way to achieve such behavior?
Check the official documentation, there is a custom basic library, but this needs to be completely redefined, because the additional query conditions of the built-in repository such as CrudRepository cannot be rewritten. I understand that the built-in convenience of jdbc cannot be used while customizing the repository. Define the interface of the repository and use other implementations such as mybatis, which loses the convenience of data jdbc.
Thank you for your answer.
The text was updated successfully, but these errors were encountered:
Hello, does spring-data-jdbc support logical pseudo-delete fields? When querying or saving, add a pseudo-delete query condition or provide a default value when saving (although it can be set through the default value of the database). Checking the source code is visible in the SqlGenerator package, and no corresponding configuration items are found. Is there a way to achieve such behavior?
Check the official documentation, there is a custom basic library, but this needs to be completely redefined, because the additional query conditions of the built-in repository such as CrudRepository cannot be rewritten. I understand that the built-in convenience of jdbc cannot be used while customizing the repository. Define the interface of the repository and use other implementations such as mybatis, which loses the convenience of data jdbc.
Thank you for your answer.
The text was updated successfully, but these errors were encountered: