Hi there,
just catching up on some old mail :-)
On 31/07/2006, at 11:56 AM, Ian Joyner wrote:
Char (1) should be more space efficient than integer in the DB (so
long as db implementation only uses one character and doesn't pad
it out).
I'm not too keen on the loose type definitions (a la C) of 0 =
false, any other value = true.
Hmm, well in this case: 0 (or 'f') == false, 1 (or 't') == true, and
the only other possibility is null which is 'unknown'.
Whichever way you choose to store the equivalent in the database you
still actually want your entity's attribute to be a Boolean and not a
String which is database implementation details that we want to be
ignorant of.
I have not tried the integer solution in Java client check boxes,
but I would hope it would not work!
That's the whole idea (i.e., beeuty) of the NSKeyValueCoding spec. It
will happily convert Number/int to [Bb]ooleans if the receiving 'key'
requires it.
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
