gorm

I have an application in migrating to MySQL and PostgreSQL and I both have different behaviors in the allocation of data. By analyzing the database created in Postgres, I realized that the numbering of ID's created in each table are not being reset in change for another table. For example, it was set in the registers 3 'Table1' and counting the ID 1 to 3. When inserted into an object of another class in another table, the ID should be started for that table, but it follows the sequence of previous and when the object is persisted in 'table2' instead his first start with the ID continues to

I have a domain class like this: class Document { String mime; String name; byte[] content; static mapping = { content lazy:true; } } and I'd like to enable lazy loading to the "content" column, because the application does some stuff without the need of access to this column. But the lazy:true option didn't work... any idea or workaround? What do you mean by the application does some stuff? and what are you trying to establish? FYI. eager and lazy loading usually has to do with relations, grails by default has lazy loading enabled. e.g." Class Book{ static belongsTo = Author String Name

class Owner { static hasMany = Dog } class Sitter { static hasMany = Dog } class Dog { static belongsTo = [Owner, Sitter] } My question is: If I create a Dog instance D, a Owner instance O, a Sitter instance S and associate D with both O and S, what happens to O when S gets deleted? Would O still have D? Since it's a cascade-delete, both S and D would get deleted, right? When what happens to O? Would it still have D? I have tested it, it follows the cascade rule: if you delete Owner, Dog will be deleted by cascade, but Sitter will remain. And it's reasonable: Sitter is independent with Owner.

My application has domain classes which have the same logical relation as photo albums and individual photographs. Using a List for the hasMany association should support backwards and forward movement within individual albums, without having to explicitly manage a position field or previous / next pointers. For example: class Album { static hasMany = [photos: Photo] List photos // Generates column `album_idx` in table for Photo. Integer size // Memoized. } class Photo { static belongsTo = [album: Album] static hasOne = [content: PhotoData] // PhotoData has byte[] field for data } class

So we are able to create different environment settings in the datasource.groovy file. And we can put common settings outside the environments node like so dataSource { pooled = false driverClassName = "org.h2.Driver" username = "sa" password = "" } environments { development { dataSource { dbCreate = "create-drop" url = "jdbc:h2:mem:devDb" } } test { dataSource { dbCreate = "update" url = "jdbc:h2:mem:testDb" } } production { dataSource { dbCreate = "update" url = "jdbc:h2:prodDb" } } } But is there a way to so that we can have certain enviroments share some properties while others share a