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
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. I have not tried the integer solution in Java
client
Hello
I use integer data for boolean
0=false
1=true
no need any code, just works fine, also on WOCheckBox.
Amedeo
On 28/lug/06, at 01:42, Ian Joyner wrote:
I just store booleans in a one character field (which you should
define as a protoype in EOModeler in the EOPrototypes entity as
Val
I just store booleans in a one character field (which you should
define as a protoype in EOModeler in the EOPrototypes entity as Value
Class NSString, Value Class (Java) String, external type char, width
1, in case this definition ever needs to change).
Then the code looks like:
st
See if this helps some:
http://en.wikibooks.org/wiki/Programming:WebObjects/EOF/Modeling/
Booleans
On Jul 27, 2006, at 12:42 PM, Theodore Petrosky wrote:
I am relatively new to WO and I don't understand how
to handle boolean values. I am just starting to play
with a database (postgresql) that
I am relatively new to WO and I don't understand how
to handle boolean values. I am just starting to play
with a database (postgresql) that I normally access
from a cocoa app that I wrote.
When I use EOModeller to reverse engineer the
table(s), the booleans come across as NSNumber class.
however p
