-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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
undo_log表自增序列 #6479
Labels
type: bug
Category issues or prs related to bug.
Comments
Thank you for your feedback; we will evaluate this requirement. |
这个问题大概在哪个版本做相关更新 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Why you need it?
ToG项目上第三方数据库管理方鉴于安全管理考虑,禁止使用pgsql的public模式,但是服务端的undo_log必须使用public模式下的自增序列
private static final String INSERT_UNDO_LOG_SQL = "INSERT INTO " + UNDO_LOG_TABLE_NAME +
" (" + ClientTableColumnsName.UNDO_LOG_ID + "," + ClientTableColumnsName.UNDO_LOG_BRANCH_XID + ", "
+ ClientTableColumnsName.UNDO_LOG_XID + ", " + ClientTableColumnsName.UNDO_LOG_CONTEXT + ", "
+ ClientTableColumnsName.UNDO_LOG_ROLLBACK_INFO + ", " + ClientTableColumnsName.UNDO_LOG_LOG_STATUS + ", "
+ ClientTableColumnsName.UNDO_LOG_LOG_CREATED + ", " + ClientTableColumnsName.UNDO_LOG_LOG_MODIFIED + ")"
+ "VALUES (nextval('undo_log_id_seq'), ?, ?, ?, ?, ?, now(), now())";
How it could be?
能否修改插入的自增序列和undo_log表一样支持配置或者插入的时候不从代码层面获取主键id
Other related information
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: