Jim, Did you ever get an answer or solution to your question? Also saw that James A. Hillyerd's message 'Null values with Torque' seems to be unresolved.
Is this a bug? Does anyone have a patch.... David > -----Original Message----- > From: Jim Downing [mailto:[EMAIL PROTECTED]] On Behalf Of > Jim Downing > Sent: Saturday, April 06, 2002 6:53 AM > To: [EMAIL PROTECTED] > Subject: Null values in torque objects > > > Hi, > > I've been using Torque for about a week, working through the > tutorial and a couple of tester programs, and came across a > problem when I started to use the framework in anger. It's > likely that I just haven't understood the thrust of what's > going on; none of this is in any way criticism. > > Is it possible to have null valued attributes in Torque > created objects? I've been getting a java.lang.VerifyError > which I traced to the BaseXXXPeer class (generated from > Peer.vm). The buildCriteria method assumes that all values > are non-null, given that it's illegal to add a null value to > a Hashtable (which Criteria extends). > > So; is it a basic condition of Torque that all attributes > should be initialized and non-null? If so, wouldn't it be > better to add default value initialization to the generated SQL? > > Thanks, > Jim Downing > [EMAIL PROTECTED] > > -- > To unsubscribe, e-mail: > <mailto:turbine-torque-user-> [EMAIL PROTECTED]> > > For additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
