> Would this change also remove the need for torque.overloadKeySetters, > which if set to true causes the creation of setters for the key fields > and PK using strings. I see two reasons this should no longer be needed: > 1 - for String fields it becomes obviously redundant > 2 - for non-string fields, you should use the proper types. My guess is > that these methods were added to help alleviate the pain caused by using > the key types in the first place.
I think that makes sense and I'd like to see some cruft removed. As long as none of the other devs have objections concerning the backwards compatibility, I'd say go for it. - Stephen -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
