The Entity Engine rather intentionally does not try to hide things like this. Generally people working on applications have access to and work with:
1. seed/setup data files 2. the database itself (for debugging, integrations, and so on) 3. the code dealing with the field (writing, querying, comparing, etc)If we just change #3 that would leave the other 2 inconsistent and confusing. Also in addition to #1 and #2 there are probably other things I'm missing in my quick thoughts on this.
-David On Oct 15, 2007, at 9:29 AM, Adam Heath wrote:
Why does GenericEntity store booleans internally as "Y" or "N"? Wouldn't it make more sense to store them as Boolean? "Y" or "N"encoding should be handled at the database layer, when reading and writing.
smime.p7s
Description: S/MIME cryptographic signature
