transient

In my Grails 1.3.7 project I have a domain class like this: class User { String login String password String name String passwordConfirmation static constraints = { login unique:true, blank:false, maxSize:45 password password:true, blank:false, size:8..45, matches: /(?=.*\d)(?=.*[a-z])(?=.*[A-Z])(?!.*\s).*/ name blank:false, maxSize:45 passwordConfirmation display:true, password:true, validator: { val, obj -> if (!obj.properties['password'].equals(val)) { return ['password.mismatch'] }} } static transients = ['passwordConfirmation'] String toString() { name } } And I'm using scaffold for the

Ok, I initially wanted to make NSSortDescriptor of a request for NSFetchedResultsController to sort based on the property in my NSManagedObject subclass, but It obviously won't do it, because NSFetchedResultsController is limited to predicates and sort descriptors that work on the fetched entity and its relations, so I decided to create a transient attribute in my data model, synthesis the property for this attribute to ivar in my NSManagedObject subclass, and sort based on it. When running it, i got while executing fetch 'NSInvalidArgumentException', reason: 'keypath isActive not found in

Possible Duplicate: Why does Java have transient variables? The transient keyword will be used to prevent serialization of a particular variable. But why should we not to serialize the data? Is there any inner security? Some classes are inherently not serializable, because they represent resources outside of the manage Java environment. For example a FileOutputStream can't really be serialized, because it represents an open file handle. The same is true for a Socket : you can't save and restore "open sockets". If you want to serialize some object that has a field of that type, then you'll have

I would like to create/update text columns in sqlite3. When i retrieve rows after the create/update, the text is '?'. Integer values are properly persisted however. My text statements look like this: const char *sql = "INSERT INTO todo(title, description, priority, status, created, expires, posx, posy, updated)" " VALUES('?', '?', '?', '?', '?', '?', '?', '?', '?');"; if (sqlite3_prepare_v2(database, sql, -1, &insert_statment, NULL) != SQLITE_OK) ... sqlite3_bind_text(update_statment, 5, [[dt stringFromDate:self.updated] UTF8String], -1, SQLITE_TRANSIENT); I've tried SQLITE_TRANSIENT as well

I was reading the source of Java's ArrayList and I came across its backing array declaration: private transient Object[] elementData; Why does this need to be transient? Why can't this class be serialized? Thanks for the help! Ernest Friedman-Hill It can be serialized; the ArrayList class just takes care of things itself, rather than using the default mechanism. Look at the writeObject() and readObject() methods in that class, which are part of the standard serialization mechanism. If you look at the source, you see that writeObject() does not save the backing array. Instead, it serializes the

I'm trying to persist Maps of properties as single JSON-encoded columns, as shown in this question . The problem I'm having is that apparently transient properties cannot be set in the default map constructor . Given any transient field: class Test { //... String foo static transients = ['foo'] } It seems that the map constructor (which Grails overrides in various ways) simply discards transient fields: groovy:000> t = new Test(foo:'bar') ===> Test : (unsaved) groovy:000> t.foo ===> null While direct assignment (through the setter method) works as expected: groovy:000> c.foo = 'bar' ===> bar