No Branch/Tag Specified
DrWrong/master
Nanyan/master
add_on_update
cantasci/added_mssql_pagination_feature
chenghuama/master
eleztian/fix/time
feature/relation
in-han/master
koron/nullable-ToDB
liuchenrang/master
lunny/belongs_to
lunny/clickhouse
lunny/db2_support
lunny/fix_join_tablename
lunny/green_plum
lunny/improve_expr
lunny/json_with_texts
lunny/limit_query
lunny/pgx_support
lunny/redis_cache_test
lunny/return_error
lunny/test_oracle2
lunny/version
master
patch
yuanfan/bugfix
godror
v.0.7.3
v0.2
v0.2.1
v0.2.2
v0.2.3
v0.3.1
v0.3.2
v0.4.1
v0.4.2
v0.4.3
v0.4.4
v0.4.5
v0.5.0
v0.5.1
v0.5.2
v0.5.3
v0.5.4
v0.5.6
v0.5.7
v0.5.8
v0.6.2
v0.6.3
v0.6.4
v0.6.5
v0.6.6
v0.7.0
v0.7.1
v0.7.2
v0.7.3
v0.7.3.1
v0.7.4
v0.7.5
v0.7.6
v0.7.7
v0.7.8
v0.7.9
v0.8.0
v0.8.1
v0.8.2
v1.0.0
v1.0.1
v1.0.2
v1.0.2-godror
v1.0.2-godror-v2
v1.0.3
v1.0.3-godror
v1.0.3-oracle
v1.0.4
v1.0.5
v1.0.6
v1.0.7
Labels
Apply labels
Clear labels
blocked
db/oracle
db/sqlserver
duplicate
invalid
kind/breaking
kind/bug
kind/build
kind/dependencies
kind/docs
kind/driver
kind/enhancement
kind/feature
kind/performance
kind/proposal
kind/question
kind/refactor
kind/regression
kind/testing
refactor
skip-changelog
wait/feedback
wait/test
wip
wontfix
No Label
blocked
db/oracle
db/sqlserver
duplicate
invalid
kind/breaking
kind/bug
kind/build
kind/dependencies
kind/docs
kind/driver
kind/enhancement
kind/feature
kind/performance
kind/proposal
kind/question
kind/refactor
kind/regression
kind/testing
refactor
skip-changelog
wait/feedback
wait/test
wip
wontfix
Milestone
Set milestone
Clear milestone
No items
No Milestone
Assignees
Assign users
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.
No due date set.
Dependencies
This issue currently doesn't have any dependencies.
Reference in new issue
There is no content yet.
Delete Branch '%!s(MISSING)'
Deleting a branch is permanent. It CANNOT be undone. Continue?
No
Yes
(1)0.x 版本insert 空数组不会报错,只是affected = 0,而现在会报 ErrNoElementsOnSlice,这在代码升级的时候会让insert方法都得重新考虑,之前只要不是err 就继续执行下面代码的逻辑都得重新审查,是否考虑过还采用原来方式?
(2)xorm 在affected 和 error 之间是如何取舍的,是否有一个原则我们可以遵循,例如“报错只包含 mysql + 网络错误 + 语法错误”,“无更新也是更新”这种
(3)这个报错和hook 也有冲突,hook的afterProcessor 是可以在hookCtx 中获取到err的,但看代码应该只有exec 里面的err 才会被hook 感知到,像 ErrNoElementsOnSlice 这种外层检查报错hook不会捕获,这对于通过hook 做监控 就存在漏报的问题