Hi Dennis, thanks for your help. On Aug 17, 11:17 pm, Dennis Clark wrote: > Null values in Transfer are covered in the wiki: > seehttp://docs.transfer-orm.com/wiki/Handling_Null_Values.cfm
I had read the docs, but obviously didn't fully understand the consequences. > If you have nullable="true" for a property and you set the property to an > empty string, the corresponding column will be set to NULL on save. When you > read the column back, the property is populated with an empty string. > > If you have nullable="false" for a property and you set the property to an > empty string, the corresponding column will be set to an empty string on > save. When you read the column back, the property is populated with an empty > string. Thanks again, it now makes sense. I had always taken them as some kind of validation... :P > If you want to be able store both NULLs and empty strings in the same > column... Actually, I want the field NOT to be null. I have already solved the issue just by not validating the object when the field is empty. But I have another problem which I'll post in another thread. > Does that make sense? Perfect sense :) Pedro. -- Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer Try out the new Transfer ORM Custom Google Search: http://www.google.com/cse/home?cx=002375903941309441958:2s7wbd5ocb8 You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en
