jdaugherty commented on code in PR #963:
URL: https://github.com/apache/grails-doc/pull/963#discussion_r2006381642
##########
src/en/ref/Database Mapping/version.adoc:
##########
@@ -28,7 +28,7 @@ class Book {
Usage: `version(string/boolean)`
-By default GORM is configured with
http://gorm.grails.org/6.0.x/hibernate/manual/index.html#locking[optimistic
locking] enabled. You can disable this by calling the `version` method with an
argument of `false`:
+By default GORM is configured with
https://gorm.grails.org/6.0.x/hibernate/manual/index.html#locking[optimistic
locking] enabled. You can disable this by calling the `version` method with an
argument of `false`:
Review Comment:
6.0.x ... we need to use the gorm verison from the bom here, no?
##########
src/en/ref/Domain Classes/belongsTo.adoc:
##########
@@ -71,4 +71,4 @@ class Book {
In these examples, both techniques create an `Author` property named `author`.
Also, the Map property can specify multiple properties and types if the class
belongs to more than one owner.
-The `belongsTo` property is simple and means you don't have to worry about the
Hibernate cascading strategies, but if you need more control over cascading you
can use the http://gorm.grails.org/6.0.x/hibernate/manual/index.html#ormdsl[ORM
DSL]. This allows fine grained control of cascading updates and deletes.
+The `belongsTo` property is simple and means you don't have to worry about the
Hibernate cascading strategies, but if you need more control over cascading you
can use the
https://gorm.grails.org/6.0.x/hibernate/manual/index.html#ormdsl[ORM DSL]. This
allows fine grained control of cascading updates and deletes.
Review Comment:
6.0.x, use the version from the bom?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
