object-persistence

I've been trying to boil down to an MCVE some code the author of another q sent me to illustrate a problem with a custom component. The component is simply a TPanel descendant which includes an embedded TDBGrid. My version of its source, and a test project are below. The problem is that if the embedded DBGrid has been created with persistent columns, when its test project is re-opened in the IDE, an exception is raised Error reading TColumn.Grid.Expanded . Property Grid does not exist. Executing the Stream method of the test project shows how this problem arises: For comparison purposes, I

I have a multi step form which uses one model object and I need to persist it between the steps. The object gets saved to the database only after the final step. I have seen people suggest using HTML.Serialize but how secure is this option? Also my model object will grow as the user fills up the form which means the hidden form field with serialized data will add up size to my HTML output. Whats the best practice for this kind of situation? I've use the TempData for this purpose. You can store an object (a copy of your model data) in TempData, and use it in the next request. If it is not set

I have a strange situation which appears to indicate a GORM cacheing problem //begin with all book.status's as UNREAD Book.list().each { book.status = Status.READ ; book.save() } println (Book.findAllByStatus (Status.READ)) //will print an empty list println (Book.list().findAll (it.status == Status.READ)) // will print all books I cannot understand why the last two queries could return different results. However if I make the following modification of book.save(flush:true) . Both of the println statements will return all books. I was under the impression that this was not necessary within a